Last month, we announced Solace VMR support for AMQP 1.0 (Advanced Message Queueing Protocol). We’ve now added AMQP 1.0 support to our 3530 and 3560 hardware messaging appliances, with the release of SolOS version 8.3.0.
SolOS version 8.3.0 also adds support for several features which we’ll explain briefly in this blog, including queue subscription exceptions, JMS non-exclusive topic endpoints, and scaling of the Access Control List (ACL) capacity of the 3560 appliance.
With AMQP now available on both the VMR (2018 update: the VMR is now referred to as Solace PubSub+) and appliances, you can develop your AMQP 1.0 applications using the VMR, and deploy on either the VMR or the hardware appliances – or a mixture of both! Learn more about AMQP 1.0 and find everything you need to quickly get started using AMQP 1.0 with Solace routers at https://solace.com/tech/amqp/
When setting up queue subscriptions containing wildcards, we’ve added the ability in SolOS version 8.3.0 to define exceptions to those wildcard subscriptions (hence the name “subscription exceptions”). For example, a queue might want to receive all messages matching the pattern “ORDERS/a*”, except for any messages matching the more specific pattern “ORDERS/acmecorp”.
With subscription exceptions, this can be achieved by configuring the following two subscriptions on the queue (where a leading ‘!’ character is used to indicate the subscription exception):
This feature allows you to “poke holes” in your wildcard queue subscriptions, which gives you a lot of flexibility in managing which messages get attracted to the queue. Learn more here.
Subscription Exceptions are available today on the hardware appliances, and will be supported on the VMR at the end of November.
Have you ever had a JMS application that received messages from a Durable Topic Endpoint (DTE), and found that one JMS consumer just wasn’t enough to handle the incoming message rate? Well, with Non-Exclusive Topic Endpoints, you can configure a single DTE to allow many consumers to connect to it at the same time. Message delivery will round-robin amongst all the connected consumers. With this feature, you can have as many as 10,000 consumers connected to a single DTE – enough to quickly handle even the biggest message bursts, no matter how complicated your message-processing functions might be.
JMS non-exclusive topic endpoints are available today on the hardware appliances, and at the end of November on the VMR.
Access Control Lists (ACLs) are used by the Solace router to control which topics clients are allowed to publish on, and which topics they may subscribe to. As more and more clients connect to the 3560, you may find you need to add new ACL rules to accommodate the new clients. In SolOS version 8.3.0, we’ve increased the number of ACL rules to 500,000 rules per 3560 appliance, ensuring that you have lots of capacity to handle your most complicated ACL scenarios.
Steve Buchko is Solace’s VP of Product Management, Core Products, leading a team that works closely with our customers, CTO, and our engineers to define Solace’s product roadmap and direction. Steve was one of our first product architects, and continues to collaborate with Solace’s product architecture team, translating the customer requirements into a robust product design.
Prior to joining Solace, Steve had a long career at Newbridge Networks (later Alcatel Canada), where his roles included product manager, product architect, and software team manager. He was responsible for the definition and development of IP routing and ATM switching features across a variety of Newbridge products. Steve was a regular attendee at the IETF, and is co-inventor of several patents in the telecommunications and networking space.[position] => [url] => https://solace.com/blog/author/sbuchko/ ) )