Handling 100 million messages a day is a solid milestone for us and we couldn’t be happier. The service was released in December 2011 and in the course of these 12 months we’ve seen strong growth. More and more cloud developers are realizing not only the benefits that message queues provide – we’ve listed a number of these reasons in a post on Top 10 Uses for a Message Queue – but also why cloud-based messaging makes so much sense.
The Rise of Distributed Cloud ComputingIn our minds, hitting this mark really just lays down a marker on the start of new era of distributed cloud-based messaging and event-handling. We frequently hear people in the space saying the cloud changes everything. And while it’s true, we’re only at the beginning of what cloud computing and elastic services can truly provide.
Much of the news on cloud computing these days is focused on PaaS and IaaS. In other words, it’s about launching servers and deploying runtime apps. But behind every cloud-application of any complexity or size lies a number of independent processes, task workloads, and connections to other systems. All this activity needs a way of gluing these pieces together. Hence, the message queue.
[Y]ou can find a message queue in nearly every major architecture profile on HighScalability. Historically they may have been introduced after a first generation architecture needed to scale up from their two tier system into something a little more capable (asynchronicity, work dispatch, load buffering, database offloading, etc). If there's anything like a standard structural component, like an arch or beam in architecture for software, it's the message queue.
From HighScalability's repost of Top 10 Uses for a Message Queue