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


Data orchestration and response consolidation using the chained design pattern has a certain level of complexity, both in the composition process itself and in the debugging process.

The process of consolidating data using a chained pattern does not occur at a single point, as we are usually accustomed to using an aggregator. With the chained design pattern, data consolidation is gradual and occurs partially at each call stage of the requests chain. The result will be finally completed at the end of all the request processing.

The longer the internal chain of calls to microservices, the longer the data consolidation process will take.

When using the chained design pattern, the Domain-Driven Design (DDD) process is necessary to reduce the number of chain calls performed internally by microservices. In order not to have a negative impact on the consumer of our application, it is essential not to have a long chain of communication between microservices...