Throughout the book, we have worked with various patterns of communication between microservices. We applied almost all the mentioned patterns, and in the course of the development process, we were remodeling our code, modifying and adding patterns in our application.

We are currently applying the following patterns in the application:

• Proxy microservice design pattern: This is applied using Nginx in the role of proxy. This pattern refers to the proxy for the OrchestratorNewsService, UsersService, and RecommendationService APIs.
• Aggregator microservice design pattern: OrchestratorNewsService performs the role of aggregator for the FamousNewsService, SportsNewsService, and PoliticsNewsServicemicroservices. 
• Branch microservice design pattern: This is the pattern that we have used to establish communication between UsersService and RecommendationService, because RecommendationService needs information synchronously from UsersService to finish the task it proposes.
• Asynchronous messaging microservice design pattern: This pattern is applied between OrchestratorNewsService and RecommendationService.

For an overview of the previous bullet points, refer to the following diagram: