Basic Structure and Topology for Applications. Learn how to make decisions about RabbitMQ exchanges, queues and bindings.
In the world of physical mail, there is a struggle to address letters and envelopes individually. In the world of email, it gets easier because you can send one letter to multiple address. But what do you do in the software world, when you need one application to communicate with multiple external processes, systems and other applications?
The "easy" way is like stuffing envelopes with copies of the same message. Only in this case, you have to re-write the message with a slightly different format and sent it to different API endpoints. The "right" way is to take advantage of systems like RabbitMQ that provide simple messaging infratructure for distributed applications.
But while there is a lot of flexibility with RabbitMQ messaging and topologies, there isn't a lot of information about how to organize things. There is very little out there that will show you how to create an exchange, routing and queue layout that makes sense for your application.
Give it a read. You will both enjoy and profit from the author's experience.
Pros: 1. The content is distilled and very practical. 2. The author story tells his experience with examples to help you profit from it by virtually going through the problem-solutioning approach. Cheers to the author for this! 3. The author has brought in some structure to topology design that you can takeaway to help you put to use at work for better communication during whiteboarding. 4. You learn by use-cases. 5. It is a short book that you can read through if you want as if you are reading a short novel ;)
Cons: - Some proof-reading and editing would have helped. This is no big deal to be though.