Published on March 16, 2014
Which messaging layer to use in a loosely coupled distributed app? ! Narahari (Hari) Allamraju ! java developer; python enthusiast working with messaging systems for 9.5 years ! http://github.com/supercoderz
Mess everyone talks to everyone
Messaging everyone talks to everyone through a single medium
Work Queue everyone queues their tasks at the same place and waits for the results
So you want to build a loosely coupled app ! ! what do you need to do?
The basics • Will the application beneﬁt by splitting up into components? • What are the components? How are they dependent on each other? • Do we need more than one instance of each to cope up with the load?
Identify the patterns • What sort of interface do we need - request-reply, publish subscribe or queuing? • Do we need to separate out messages into various types? • Do we need schemas for the messages or free form? • Are there any components that have a higher or lower throughput than others?
Latency, routing, priority • Which components need the message yesterday; and which can wait till end of day? • Do we need to expire messages when they are too late? • How easily can we route messages? • Can we make some messages take highest priority?
Build, Manage and Support • Do we have a suitable API? • Easy to provision and manage • Good monitoring • Guaranteed delivery of messages • Should be persist messages to disk for crash recovery? • Cleanup in case of issues
A few options • RabbitMQ • ZeroMQ • Redis • A database • RPC
Considering future growth • What if the loads increased by 15%? • What if we had a consistent heavy run for 24 hours or more? • Storage costs etc • If we have to switch to a different underlying - how hard is it? Tokyo Metro
Questions! • This presentation can be found on slideshare at - http://goo.gl/KVJxoE ! • The version with speaker notes will be available soon
Presentación que realice en el Evento Nacional de Gobierno Abierto, realizado los ...
In this presentation we will describe our experience developing with a highly dyna...
Presentation to the LITA Forum 7th November 2014 Albuquerque, NM
Un recorrido por los cambios que nos generará el wearabletech en el futuro
Um paralelo entre as novidades & mercado em Wearable Computing e Tecnologias Assis...
Which messaging layer should you use if you want to build a loosely coupled distributed Python app? by Narahari Allamraju (speaking)
Communication between layers is explicit and loosely coupled. ... use either a messaging router ... with the message bus, there is no ...
... we've been seeking to create architectures and systems that are more loosely coupled. Loosely coupled ... modern distributed ... Web App pings the ...
Share Demonstration of a Loosely Coupled M2M System using Arduino, Android and Wiki Software.
Home; Documents; The Chubby lock service for loosely- coupled distributed systems
With a Service Oriented Architecture ... distributed software that facilitates loosely ... a loosely coupled (often asynchronous), message ...
Home; Documents; Loosely Coupled Parallelism: Clusters. Context We have studied older archictures for loosely coupled parallelism, such as mesh’s ...
Home; Documents; 1 Loosely coupled OPC client used to animate GIS Mariusz Postół Maciej Zbrzezny www.cas.eu.