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

Understanding the pattern


In the previous chapters, we saw how to apply some very interesting patterns, and we could observe that each of these patterns has a very specific utility. In this sense, there are patterns that enable technical functionality, such as scalability, availability, and resilience. We also saw that there are other patterns that focus on enabling the business layer.

This is the case that occurs when we compare the aggregator design pattern and the chained design pattern. The two patterns bring improvements to the business, but it is very clear that the aggregator design pattern is aimed more at the technical part, and the chained design pattern looks for a solution to serve the business, where, in some cases, the solution may not be the healthiest option for the application.

The branch design pattern is an extension of the aggregator design pattern that enables simultaneous processing of responses from two chains of microservices. The branch seeks to be an intermediate...