March 31, 2009 at 3:00 pm by Rob Ciampa
We recently made an announcement about our joining the Advanced Message Queuing Protocol (AMQP) working group. For anyone who has worked with standards bodies, this may be akin to a B-grade soap opera sprinkled with politics, protagonists, antagonists and an ever-changing plot line. I’m sure there will be some of that (though there are some great people involved), but our focus is on the end game: fundamentally changing middleware. AMQP represents a movement in that direction. Like comparable endeavors, this is and will be a continual process. Expect more changes as companies adopt and AMQP is road tested, which, of course, is a normal part of the process.
We’ve made the case here many times against legacy messaging architectures, but it’s just as true with their queuing system alter-egos. We also continue to argue that messaging has to go through the same critical transition to hardware as network systems did. AMQP (no pun intended) is queued up for that. The biggest challenge is not whether adoption will occur, but how quickly it will happen. That’s an important variable. Hyper-efficiency and blazing speed may well be the recipe for faster market adoption, but it’s going to take some hardware acceleration to bake it.
=rob.ciampa
Skip navigation
