Book Image

Microservice Patterns and Best Practices

By : Vinicius Feitosa Pacheco
Book Image

Microservice Patterns and Best Practices

By: Vinicius Feitosa Pacheco

Overview of this book

Microservices are a hot trend in the development world right now. Many enterprises have adopted this approach to achieve agility and the continuous delivery of applications to gain a competitive advantage. This book will take you through different design patterns at different stages of the microservice application development along with their best practices. Microservice Patterns and Best Practices starts with the learning of microservices key concepts and showing how to make the right choices while designing microservices. You will then move onto internal microservices application patterns, such as caching strategy, asynchronism, CQRS and event sourcing, circuit breaker, and bulkheads. As you progress, you'll learn the design patterns of microservices. The book will guide you on where to use the perfect design pattern at the application development stage and how to break monolithic application into microservices. You will also be taken through the best practices and patterns involved while testing, securing, and deploying your microservice application. At the end of the book, you will easily be able to create interoperable microservices, which are testable and prepared for optimum performance.
Table of Contents (20 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Data orchestration and response consolidation


The level of complexity in the data composition of the branch design pattern can be considered one of the highest. The high complexity is due to the fact that, when using the branch, we are using both the composition of data and the orchestration of data, either in alternation or simultaneously.

Using the branch as the design pattern, the most common scenario is that the composition of the data occurs in the internal layer of microservices, and, obviously, the data orchestration in the public facing layer. It is worth remembering that a more complex data search implies more time and machine resources to create a response with total integrity.

In the following diagram, we have a process where data composition is being performed in the internal layer, and the orchestration of data in the public facing layer:

Let's understand the flow of the diagram we just observed:

  1. First, the Microservice Aggregator receives a request from the API and needs to consolidate...