The previous chapters of this book focused on the setup of a successful microservice architecture using RabbitMQ at the example company Complete Car (CC). Many RabbitMQ features were included, however, no system is complete without an understanding of the best practices to use in its implementation. As with all production systems, proper monitoring and alerts are also needed to stay on top of things.
CC's cluster is stable and there are no performance issues. This chapter summarizes the key takeaways learned from CC's system, including best practices and recommendations for queues, routing, exchanges, message handling, and more.
This chapter explores the following topics:
- How to avoid losing messages ...
