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 chained design pattern allows scalability in the y-axis, x-axis, and z-axis models, all of which are related to how many instances of a service are available for access through a proxy to redirect requests.

It is very common to use the proxy design pattern with the chained design pattern. This approach is adopted so that the proxy is responsible for indicating the microservice through which the chained pattern will begin the possible communication between microservices to compose a response.

Another common practice is that each microservice, using the chained design pattern, has its own server, such as Nginx. It is a slightly different approach than we have adopted so far, since we have an application server, and we manipulate the instances.

A common scalability model is shown in the following diagram, where, after identifying which microservice in the communication chain is slow, new instances of the identified microservice are created to improve performance. In the...