adoption. Apache ActiveMQ Artemis is designed with usability in mind. Written in Java. Runs on any platform with a Java 8+ runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using destinationCache element, you can toggle on the destination cache to NIO to interface with the file system. This provides extremely good performance and runs on any platform where there's a Java 6+ runtime. Linux Asynchronous IO The second implementation uses a thin

• Apache ActiveMQ Artemis is designed with usability in mind. • Written in Java. Runs on any platform with a Java 11+ runtime, that’s everything from Windows desktops to IBM mainframes. • Amazing (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my- link-name. If the Terminus Durability is configured as NONE then scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

• Apache ActiveMQ Artemis is designed with usability in mind. • Written in Java. Runs on any platform with a Java 11+ runtime, that’s everything from Windows desktops to IBM mainframes. • Amazing (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my- link-name. If the Terminus Durability is configured as NONE then scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

• Apache ActiveMQ Artemis is designed with usability in mind. • Written in Java. Runs on any platform with a Java 11+ runtime, that’s everything from Windows desktops to IBM mainframes. • Amazing (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my- link-name. If the Terminus Durability is configured as NONE then scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

• Apache ActiveMQ Artemis is designed with usability in mind. • Written in Java. Runs on any platform with a Java 11+ runtime, that’s everything from Windows desktops to IBM mainframes. • Amazing (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my- link-name. If the Terminus Durability is configured as NONE then scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

• Apache ActiveMQ Artemis is designed with usability in mind. • Written in Java. Runs on any platform with a Java 11+ runtime, that’s everything from Windows desktops to IBM mainframes. • Amazing (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my- link-name. If the Terminus Durability is configured as NONE then scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

adoption. Apache ActiveMQ Artemis is designed with usability in mind. Written in Java. Runs on any platform with a Java 8+ runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my-link-name . If the Terminus Durability is configured as NONE scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

adoption. Apache ActiveMQ Artemis is designed with usability in mind. Written in Java. Runs on any platform with a Java 8+ runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my-link-name . If the Terminus Durability is configured as NONE scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache

adoption. Apache ActiveMQ Artemis is designed with usability in mind. Written in Java. Runs on any platform with a Java 8+ runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my-link-name . If the Terminus Durability is configured as NONE scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to

adoption. Apache ActiveMQ Artemis is designed with usability in mind. Written in Java. Runs on any platform with a Java 8+ runtime, that's everything from Windows desktops to IBM mainframes. Amazing performance (similar to a JMS durable subscription) and given a name made up from the container id and the link name, something like my-container-id:my-link-name . If the Terminus Durability is configured as NONE scenario where destinations (addresses) are permanent broker side, such as they are managed by a platform or operations team. using cacheDestinations element, you can toggle on the destination cache to