amqp.org/about/what “The capable, commoditized, multi-vendor communications ecosystem which AMQP enables “The capable, commoditized, multi-vendor communications ecosystem which AMQP enables creates opportunities for commerce and innovation “The capable, commoditized, multi-vendor communications ecosystem which AMQP enables creates opportunities for commerce and innovation which can transform the way business is done “The capable, commoditized, multi-vendor communications ecosystem which AMQP enables creates opportunities for commerce and innovation which can transform the way business is done on the Internet “The capable, commoditized, multi-vendor communications ecosystem which AMQP enables creates opportunities for commerce and innovation which can transform the way business is done on the Internet, and in the Cloud.”
“open standard application layer protocol for message-oriented middleware” https://en.wikipedia.org/wiki/ Advanced_Message_Queuing_Protocol “open standard application layer protocol for message-oriented middleware”
Different messages for different client needs 30 master data client Owns additional user data related to master data • User account aka master data record removed Caches master data • If master data updated or removed Mirrors master data • Updated master data
No guaranteed order – aim for commutativity Order of messages not guarantueed Commutativity Complement with synchronous API (e.g. REST) • most recent data • leading system • message consumers follow up with REST if necessary Small payload • easier on the broker • just enough data for consumer to decide about making REST request 35
No exactly-once delivery – aim for idem-potent messages Duplicated messages • possible e.g. if producer re-sends message after connection failure • use idem-potent message handling Lost messages • acceptable for usecase? • e.g. consider rebuilding mirror / cache occasionally 36
Flexible Routing via different Exchange Types Direct Exchange • routes to all queues whose binding_key equals routing_key Fanout Exchange • broadcasts to every queue it has a binding for • ignores routing key and queue name Topic Exchange • dot-separated words as routing keys, plus wildcards • routing on multiple attributes Header Exchange • based on headers, not routing keys • routing on multiple attributes 50
titanoboa
linedevth
finengine
whywaita
ryomaru0825
line_developers
shimacos
hiashisan
yamahiro
nagiss
konifar
unclejoe
smashingmag
destraynor
roundedbygravity
garrettdimon
marktimemedia
carmenintech
sachag
mongodb
sstephenson
addyosmani
reverentgeek
yeseniaperezcruz