Pros and cons of the asynchronous messaging design pattern
The asynchronous messaging design pattern is complex to understand initially, but it offers extreme scalability. Understanding the pattern, practicing creating proofs of concept, and choosing the tools well, makes your application have scalability and resilience and reduces the complexity of the pattern.
Some examples of the good points that the pattern offers us are:
- Independent scalability
- Extreme scalability
- Lazy processing
- Encapsulation of accesses to microservices
However, we must also understand some negative points of the pattern:
- Complexity in the monitoring of requisitions
- Complexity of the initial understanding of the pattern
- Difficulty of debugging
The complexity of the asynchronous messaging design pattern should not serve as a barrier for using the pattern. A good domain design and choosing the tools to work well with are fundamental to the full operation of the microservices that use the pattern. Any initial problems presented...