![]() It typically requires application-level bridging to move messages from one system to another and to translate between their proprietary message formats. ![]() In the Java community, language-specific API standards like Java Message Service (JMS) and the Spring Framework's abstractions have alleviated that pain somewhat, but have a narrow feature scope and exclude developers using other languages.įurthermore, connecting messaging brokers from different vendors is tricky. ![]() It results in a degree of dependence on that vendor, since porting an application to a different product requires code changes in all the connected applications. It means that once you've selected a particular vendor's messaging broker, you must use that vendor's libraries to connect your client applications to that broker. Traditionally, message-oriented middleware products have used proprietary protocols for communication between client applications and brokers. Introduction: What is AMQP 1.0 and why is it important? All these components can connect to Service Bus and seamlessly exchange structured business messages efficiently and at full fidelity. You can construct applications using components that are built using different languages and frameworks, and that run on different operating systems. AMQP 1.0 is an ISO and IEC standard ( ISO 19464:20149).ĪMQP enables you to build cross-platform, hybrid applications using a vendor-neutral and implementation-neutral, open standard protocol. Microsoft has been engaged with partners across the industry, both customers and vendors of competing messaging brokers, to develop and evolve AMQP over the past decade, with new extensions being developed in the OASIS AMQP Technical Committee. The Azure Service Bus cloud service uses the AMQP 1.0 as its primary means of communication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |