Pride and zombie processes, or how not to build a message queue system
Published on: Mar 4, 2016
Transcripts - Pride and zombie processes, or how not to build a message queue system
Pride and zombie processes
Or, how not to develop a message queue system
It is a truth universally acknowledged, that
components of a distributed system in
possession of data must be in want of a method
of sharing it.
Mama, we have an engagement...
Messaging architectures are generally push; it
is often more efficient.
Data eating zombies like a byte
Who should we invite to the dance?
What messages are being sent?
Where are your firewalls and what ports are
What messaging systems do you have?
And pray, how should we converse?
Do you have one or many protocols?
If the latter, can you separate the networks?
Can you forward the messages?
Smaller messages are more effective than larger ones
Brokers may not know that consumers are not alive and send
data to them.
Protocols do not talk to each other – without writing code
Network forwarding can be used – at a speed cost
Are relevant firewalls and ports open across the network?
Use messaging gateway pattern rather than direct connections
Zero MQ (http://zeromq.org/)
ZeroMQ Guide - http://zguide.zeromq.org/page:all
RabbitMQ in Action - http://www.manning.com/videla/
ActiveMQ in Action - http://www.manning.com/snyder/