WTF Is Messaging And Why You Should Use It?

WTF Is Messaging And Why You Should Use It? @botanicus RabbitMQ team of VMwareSunday, 12 June 2011

I slept only 3 hours, Club-mate is the only thing which keeps me goin’ ... but I’ll do my best :) Club-mate FTW!Sunday, 12 June 2011

About Me Ruby & JS contractor RabbitMQ team of VMware London, UK http://twitter.com/botanicus http://blog.101ideas.czSunday, 12 June 2011

What Is Messaging? Sending messages between isolated entities (usually apps, but can be also threads, as in Erlang). Usually through a messaging broker. Asynchronous, suitable for distributed systems. Push, not pull.Sunday, 12 June 2011

From http://www.j5live.comSunday, 12 June 2011

How Can You Beneﬁt? Better design of apps. Scalability. Robustness.Sunday, 12 June 2011

#1 Better Design, Easier Maintainance Decoupling -> small, isolated apps. Greatly reduces complexity. Isolation -> its easy to rewrite just the critical parts into Java or C. Simple integration with legacy systems, no need to rewrite everything. Its dead-easy to inspect whats going through.Sunday, 12 June 2011

Sunday, 12 June 2011

#2 Scalability Improve responsiveness by doing CPU-intensive tasks later in an asynchronous manner. Scale only the parts which requires it.Sunday, 12 June 2011

#3 Robustness Backend deployment with no downtime (see the schema). Message persistency. Acknowledgements (Ive done it, send me the next task).Sunday, 12 June 2011

What if the service would go ofﬂine?Sunday, 12 June 2011

Pub/Sub Publishers do not send messages to speciﬁc subscribers. Published messages are characterised into classes, without knowledge of the subscribers. Subscribers express interest in some classes, and only receive messages they want.Sunday, 12 June 2011

Other Use-Cases From a browser utilising websockets (games development etc). Remote procedure call.Sunday, 12 June 2011

#1 AMQP in BBC Realtime Tweets Processing. As middlewares (download, process, store to S3). 1000 tweets/sec = about 90 million a day.Sunday, 12 June 2011

Protocols & APIs AMQP STOMP: HTTP-like protocol, headers & body, request/response JMS Amazon Simple Queue Service XMPP (well, kind of) WebsocketsSunday, 12 June 2011

AMQP Invented by JP Morgan. Most widely used. Binary protocol with minimal overhead. http://www.rabbitmq.com/getstarted.htmlSunday, 12 June 2011

RabbitMQ AMQP natively, STOMP, XMPP by plugins. Most widely used OSS AMQP broker. A lot of plugins available, writing new ones is quite easy (Erlang).Sunday, 12 June 2011

ZeroMQ Brokerless, provides socket-like API. Supports advanced routing. Leads to decentralised architecture.Sunday, 12 June 2011

Questions please!Sunday, 12 June 2011

Cheers for your attention!Sunday, 12 June 2011

http://www.rubyinside.com	4535
http://ruby.collected.info	193
url_unknown	67
http://blog.101ideas.cz	61
http://www.slideshare.net	10
http://feeds.feedburner.com	8
http://www.techgig.com	4
http://feedproxy.google.com	4
https://twitter.com	4
http://twitter.com	2
http://xianguo.com	2
http://webcache.googleusercontent.com	2
http://translate.googleusercontent.com	1

WTF Is Messaging And Why You Should Use It?

by botanicus on May 17, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

13 Embeds 4,893

Statistics

WTF Is Messaging And Why You Should Use It? — Presentation Transcript