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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides pattern with no tight relationship between requests and responses. Most messaging systems also support a request- response mode but this is not a primary feature of messaging systems. Designing systems they don't have brittle dependencies on each other. Messaging styles Messaging systems normally support two main styles of asynchronous messaging: message queue messaging (also known as point-to-point

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. Our ground-breaking high performance journal provides x Virtual Topic naming abilities. SSL Certificate revocation list. Last-value queue support for OpenWire. Support masked passwords in bootstrap.xm and login.config Configurable broker plugin implementation Versions 9 Highlights: Web admin console! Critical Analysis and deadlock detection on broker Support Netty native kqueue on Mac. Last-value queue for AMQP Upgrading from 2.2.0 1. If you desire to

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. Our ground-breaking high performance journal provides features or improvements. 2.6.0 Full release notes. Highlights: Support regular expressions for matching client certificates. Support SASL_EXTERNAL for AMQP clients. New examples showing virtual topic x Virtual Topic naming abilities. SSL Certificate revocation list. Last-value queue support for OpenWire. Support masked passwords in bootstrap.xm and login.config Configurable broker plugin implementation