AMQP for dummies - A guide for managers

2008-10-28 Software-Engineering AMQP

(I start to like this "plane blogging" thing :))

Adrian blogged about Microsoft embracing AMQP.

Just from a technical point of view this is good news (assuming it will help the adoption of the Advanced Message Queueing Protocol (AMQP)), because AMQP is a very cool (and extremely well thought through) standard.

Given that there might be a renewed interest in the standard, let me just try to explain (again) what it is good for: The main benefit of AMQP (besides a couple of very cool features in the standard itself) is that it will (finally and for the first time) allow messaging stacks to interoperate. Today we have lots of good payload formats/protocols (e.g. XML) and even better standard APIs (e.g. JMS), but no standard wire-level protocol to allow one messaging stack talk to another. That means that currently all of your messaging endpoints need to have the same message stack. This creates a huge, hidden vendor lock-in. Yes, your JMS API allows your to replace a JMS provider with another one, but then you need to do it for all endpoints at the same time, because the wire-level protocol is different (and proprietary) for each and every message broker implementation.

Means right now you can only build homogenous messaging infrastructures. AMQP would allow you to build heterogenous messaging infrastructures, break the vendor lock-in and enjoy the power of choice. AMQP is the HTTP of messaging. I see AMQP as an enabler for

Recent Posts