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

Pattern scalability


The branch design pattern is a combination of the chained pattern and the aggregator pattern. Therefore, all scalability and availability models that apply to each of them can be used by the branch design pattern. Obviously, there are some caveats.

Following the scalability cube model, we can apply the x-axis, y-axis, and z-axis. However, the axis is used differently for each part of the pattern.

In the case of orchestrating microservices, only the y-axis and x-axis can be applied. The reason for this limitation is the fact that the orchestrator does not have any access to data other than that sent by the other microservices with which it is communicating.

When we talk about the microservices responsible for manipulating data, the subject is different. In this case, yes, all axes can be applied to provide scalability for the application.

An important point to note is that if the engineering team made the choice to use a physical component as the communication layer between...