Distributed systems require sharing data between components. When developing a message queue system, issues can arise from zombie processes that are sent data but are not alive to receive it. Effective messaging architectures consider multiple factors such as message size, protocol compatibility across networks, and ensuring relevant firewalls and ports are open for communication. References for further reading on message queue systems like ZeroMQ, RabbitMQ and ActiveMQ are provided.

1. Pride and zombie processes
Or, how not to develop a message queue system

2. 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.

3. Mama, we have an engagement...


Messaging architectures are generally push; it
is often more efficient.
Data eating zombies like a byte

4. Who should we invite to the dance?



What messages are being sent?
Where are your firewalls and what ports are
open?
What messaging systems do you have?

5. 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?

6. Issues
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

7. Some references
Zero MQ (http://zeromq.org/)
ZeroMQ Guide - http://zguide.zeromq.org/page:all
RabbitMQ (http://www.rabbitmq.com/)
RabbitMQ in Action - http://www.manning.com/videla/
ActiveMQ (http://activemq.apache.org/)
ActiveMQ in Action - http://www.manning.com/snyder/

8. Any questions?
Twitter: iainemsley
Website: austgate.co.uk