Messaging,AMQP,andCondorHuhWhatWhy.pptVIP

Messaging, AMQP, and CondorHuh? What? Why? Some commonly desired properties for distributed system building blocks We want communication to be Reliable Secure Durable Asynchronous delivery Scalable Available Routable Multicast etc Addressable naming Semantic guarantees Flexible Manageable Filterable Transformable How well does UDP fare w/ the list on the left? TCP? Common needs led enterprise developers to adopt Message Oriented Middleware MOM Lots of solutions available So what is wrong in paradise? AMQP Motivation AMQP was born of frustration MOM needs to be everywhere to be useful dominant solutions are proprietary too expensive for everyday use Cloud-scale they don’t interoperate has resulted in lots of ad-hoc home-brew how hard can middleware be? Middleware Hell 100’s of applications 10,000’s of links every connection different massive waste of effort The Internet’s missing standard Why has no one done this before? The AMQP Working Group Set up by JPMorgan in 2006 Goal to make Message Oriented Middleware pervasive Make it practical, useful, interoperable Bring together users and vendors to solve the problem We say AMQP is an “Internet Protocol for Business Messaging” so end users feel a connection to the technology. AMQP aspires to define MOM Ubiquitous Unencumbered AMQP Intellectual Property Policy Unambiguous Right to Implement The Authors each hereby grants to you a worldwide, perpetual, royalty-free, non-transferable, nonexclusive license to i copy, display, distribute and implement the Advanced Messaging Queue Protocol AMQP Specification and ii the Licensed Claims that are held by the Authors, all for the purpose of implementing the Advanced Messaging Queue Protocol Specification. Licensed Claims means those claims of a patent or patent application, throughout the world, excluding design patents and design registrations, owned or controlled, or that can be sublicensed without fee and in compliance with the requirements of this Ag