Microservices architecture patterns

So far, we have seen that microservices architecture is based on the functional decomposition that produces independent, self-sufficient services that may have different ways of communicating with the outside world using well-defined interfaces. This favors low coupling and well-defined functions, allowing high cohesion (well-defined responsibilities with a reduced number of functions).

Although the services act independently, the purpose of these services is to create an application—that is, a set of business-related functionalities. 

Based on these characteristics, we can extract some patterns that can be used for the implementation of the microservices architecture. Here are some of these patterns:

• Aggregator pattern
• Proxy pattern
• Chained pattern
• Branch pattern
• Asynchronous messaging pattern

 

Aggregator pattern

As the name itself suggests, this pattern establishes the existence or creation of a somewhat more complex service that invokes the functions of more...