Ram Jeyaraman, Senior Standards Professional, Microsoft Open Technologies, Inc. and co-Chair of the OASIS AMQP Technical Committee
Brian Benz, Senior Technical Evangelist, Microsoft Open Technologies, Inc.
I am excited and proud to share the news that Advanced Message Queuing Protocol (AMQP) v1.0 has been approved as an International Standard (ISO 19464) by ISO/IEC Joint Technical Committee (JTC) 1. Congratulations to the OASIS AMQP Technical Committee for achieving this important milestone. Here’s the official announcement from OASIS.
This is the result of the collective work of many talented people across many organizations (Bank of America, Cisco Systems, Credit Suisse, Deutsche Boerse AG, JPMorgan Chase Bank N.A., Microsoft, Red Hat, Software AG Inc., US Department of Homeland Security, VMware Inc., and many others) who have collaborated to accomplish the common goal of creating an open interoperable and inherently efficient messaging protocol for use in a wide variety of messaging scenarios and communication patterns.
International standardization is another step towards creating an open interoperable ecosystem for AMQP. The standardization process is intentionally iterative and consensus-driven with the goal of delivering a technically complete standard that can be broadly adopted by nations around the world.
I’m grateful for the unique opportunity to serve as a co-Chair of the OASIS AMQP Technical Committee and help lead this dynamic group to drive AMQP to where it is today as an open interoperable messaging protocol. This productive collaboration spans many years, including the approval of AMQP 1.0 as an OASIS Standard in October 2012, and the ongoing development of extensions that have enhanced AMQP capabilities.
Here are some recent Blog posts from John O’Hara (Originator of AMQP), and Red Hat, who are sharing what they have to say about this achievement. Also have a look at John O'Hara's presentation on AMQP - ISO 19464 - Connecting Business for Value.
As an efficient application layer binary protocol, AMQP enables new possibilities in messaging that scale from devices to the cloud. The AMQP specification enables enterprises to more easily exchange messages between applications through a variety of common development languages and offers organizations an easier, more secure approach to passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported:
- Between applications,
- Among organizations,
- Across distributed computing environments,
- And within mobile infrastructures.
You can read more on AMQP and its business value here, and below are more resources to consider:
- For a list of related vendor-supported products, open source projects, and details regarding customer usage and success, visit the AMQP website: http://www.amqp.org/about/examples.
- If you’re a developer getting started with AMQP, we highly recommend that you read this overview.
- For additional guidance, this Service Bus AMQP Developer's Guide will help you get started with AMQP for the Microsoft Azure Service Bus using .NET, Java Message Service (JMS), Python, PHP or C. Using Service Bus from Python, PHP, and C is accomplished via use of Apache Qpid Proton library. You may also find some value from Scott Guthrie’s blog post - Walkthrough of How to Build a Pub/Sub Solution using AMQP
Whether you’re a novice user or an active contributor to the community, we’d like to hear how your experiences with AMQP by leaving comments here or by connecting with the community and joining the conversation on LinkedIn, Twitter, and Stack Overflow.
All of us at MS Open Tech are looking forward to continuing the collaboration with the AMQP community in the standards area (for example work on AMQP extensions) and open source projects (such as for example Apache Qpid Proton library).