The AMQP protocol’s broad adoption relies upon the Magic Triangle.
Earlier this month I had a chat with John O’Hara, the founder of the AMQP Working Group and the Global Head of Architecture for Commodities at Bank of America. We covered many topics; however the overriding theme was regarding the future of AMQP and the MQ market in general.
Telemetry has for a long time been associated with Formula One racing.
Large banks of software engineers pour over screens as the cars scream round circuits and interpret data as it arrives real time from the cars to decide crucial events such as when to change tyres, when and how much to refill, to advise changes in driving style and the list is endless.
The answer is very. Client data is always vitally important and combining that with financial details provides a red hot issue that banks, not surprisingly take very, very seriously.
So when a supplier like stormmq comes along and offers a Cloud based Message Queue Service, a discerning CIO will firstly take a view of the commercial proposition (which needs to be convincing) before even considering whether the Service will stand up to the scrutiny of his or her internal audit security teams.
stormmq, the enterprise‐class message queuing platform company, today announced that it has partnered with Kaazing, the leading innovator in HTML 5 WebSocket technology.
stormmq is integrating Kaazing’s WebSocket Gateway technology with its cloudmessaging services to give businesses the ability to deploy sophisticated, real‐time and massively scalable applications to any end‐device.
Superficially, stormmq seems to be like Amazon’s SQS, but they have very different message properties.
Amazon SQS and stormmq both support message properties. These are meta data that can be attached to your message (a bit like headers are attached to email) that help an application process a message. A classic example is a message id. However, both systems differ vastly in the range of properties offered, their granularity and understanding by the server.
stormmq is built around the AMQP protocol, a protocol that was designed when a group of vendors got together with a few users with a vision to build a reliable and open protocol for the MQ market.
The goal was to produce the next generation MQ protocol to replace the incumbent proprietary standards. Over the past few years this protocol has passed through a few iterations but the current agreed standard is AMQP 0‐9‐1.