Examples of architectures designed to run on Amazon Web Services are a great way to illustrate the necessary design changes and patterns associated with a cloud deployment methodology.
Soocial.com, a "one address book solution to contact management" runs entirely on AWS and uses some interesting technologies to make their service work, including RabbitMQ, an open-source implementation of AMQP, the emerging standard for high-performance enterprise messaging. (I've written about AMQP and RabbitMQ here, and here in the past.)
One of the most interesting things is how the architecture isn't dramatically different than it would be if you were to build an on-premise version--except that Soocial is able to take advantage the Amazon Web Services EC2's scale, hot-standby, and backups. It's definitely worth learning more about if you are interested in the cloud.
The Rabbit team just released a RabbitMQ to XMPP gateway proof-of-concept.
RabbitMQ is an implementation of AMQP, the emerging open source standard for high performance enterprise messaging. Think of AMQP as the open source version of something like MQ Series or other high-volume JMS servers.XMPP is open XML technology for presence and real-time communication.
Message volume shouldn't be a problem for services like Twitter. RabbitMQ with an XMPP gateway might be part of the the solution. The combination means you can inject very high volumes of messages into IM or other XMPP enabled applications with far fewer scale issues.
For the geeks:
The mod_rabbitmq module implements an ejabberd extension module which gateways AMQP (as implemented by RabbitMQ) to XMPP.
Via James Governor Monkchips on Twitter.
- prev
- 1
- next
