Microsoft announces AMQP 1.0 support has been released on Windows Azure Service bus

Over the past five years, Microsoft has worked with other companies to develop advanced Message Queuing Protocol (AMQP) standards. The more than 20 companies include technology suppliers, including red hats, http://www.aliyun.com/zixun/aggregation/17954.html, and businesses like "> Morgan Chase" and "Credit Suisse". The goal is to establish an open, line-level messaging protocol standard that makes interoperability between different vendors simpler. Back in October 2012, the Oasis Standards Organization announced the adoption of AMQP 1.0 as the Oasis standard, and on the same day we released a preview of the Windows Azure Service bus that executes AMQP1.0.

Today, I am pleased to announce that the AMQP 1.0 support has been released in the Windows Azure Service bus and is officially supplied (GA)-it can already be actually put into application for enterprise SLA support.

Interoperable messages

The announcement was significant. With support for AMQP 1.0, you can now use the Windows Azure Service bus to create applications that can use a wide variety of message stores, use different languages, or run on different operating systems-now you can use efficient, binary, and line-level protocols to communicate.

Because AMQP 1.0 defines a portable data representation, this means from. NET programs sent to the service bus can be read by Java programs or python/ruby/php footsteps without losing any structure or message content. In Java, the standard Java Messaging Service (JMS) API is supported so that existing Java applications can be ported directly from any other JMS provider to the service bus.

The end result is a powerful middleware that can be used to create distributed systems that connect across internal deployments/cloud environments or applications that run across multiple cloud providers.

Demonstrates how to use AMQP to create a pub solution

To highlight how easy it is to use this new information support, I'll show you how to create a simple. NET console application, which uses the Publish/Subscribe message mode to send messages to the receiving application written by Java,python and PHP. Windows Azure Service Bus now provides all the necessary support for pub messaging to facilitate the use of open AMQP protocols and existing messaging frameworks.

. NET sender application sends a message to the service bus "subject"-a persistent messaging intermediary. Unlike queues, each message in a queue is handled by a single consumer application, and the theme provides one-to-many forms of communication, using the Publish/subscribe model. It allows you to register multiple subscriptions to a topic-when a message is sent to a topic, each subscription can handle the message independently.

You can imagine each subscription as a virtual persistent queue that receives a copy of the message sent to the subject. You can choose to register filtering rules for any subscription on the subject, allowing topic subscriptions to filter/restrict receipt of messages sent to the subject. Enables you to selectively process large numbers of messages across a large number of users and applications.

In this scenario we will let. NET console applications to send messages to the "Scottmessages" topic, and then set up their own subscriptions for the three listening applications, written separately by Java, Python, and PHP-to receive and process messages.