This article is contributed. See the original author and article here.
Azure Service Bus is the enterprise messaging PaaS of choice for customers looking for a cloud native service with familiar queue and topic subscription semantics using the industry driven Advanced Message Queuing Protocol (AMQP). By virtue of being a modern PaaS offering on Azure, Azure Service Bus aims to bring deeper integrations with Azure’s services along with high availability, secure design and scalability built into the platform as a first-class experience to the application integration space.
As businesses, from retail to finance, and manufacturing to transportation, accelerate their digitalization efforts and further embrace the cloud, many are moving and modernizing existing Java-based workloads that lean on enterprise messaging brokers like IBM MQ, TIBCO EMS or JBoss A-MQ through the JMS 2.0 application interface.
With Azure Service Bus Premium expanding its feature set to provide JMS 2.0 specification compliance, businesses can leave the complexity and cost of licensing, maintaining, and operating these legacy broker infrastructures behind and switch to Azure Service Bus as the reliable and highly available backbone of their critical applications. For multi-site systems that use centralized broker infrastructures in on-premises datacenters, Azure Service Bus is also a very attractive, cost efficient, managed PaaS alternative to running such infrastructure even if many of the attached workloads remain on-premises.
Today, we’re ecstatic to announce the general availability for Java Message Service (JMS) 2.0 for enterprise workloads on Azure Service Bus Premium tier.
Seamlessly migrate and connect existing applications with Azure Service Bus over AMQP
By leveraging Azure Service Bus JMS support, customers can avoid the overhead of procuring licenses, managing an enterprise messaging broker on their own IaaS Compute, simplify cost management with a fixed price per messaging unit, and by leveraging automatic scale up/down to address variability in workloads.
We also continue to promise the simplicity of configuration only code changes to enable our customers to bring their existing JMS client applications.
Utilize existing JMS enterprise application integration (EAI) connectors and tooling to interact with Azure Service Bus
With full support for Java Message Service (JMS) 2.0 on Azure Service Bus, the possibilities for interacting with Azure Service Bus are virtually endless. Our customers can now utilize existing EAI connectors that leverage JMS APIs to perform management and data plane operations on Azure Service Bus.
We’ve also added support for the JMS toolbox tool to interact with Azure Service Bus, enabling customers to have a familiar tool used with various JMS message brokers.
Get Started Today
To learn more about Azure Service Bus and try out the Java Message Service (JMS 2.0), check out the below links
- Use Java Message Service 2.0 API with Azure Service Bus Premium
- Migrate existing Java Message Service (JMS) 2.0 applications from Apache MQ to Azure Service Bus
- How to use the Spring Boot starer for Azure Service Bus JMS
- Use JMS Toolbox to interact with Azure Service Bus
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.