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

Process sequence anti-pattern


The process sequence anti-pattern is a microservice version of a known anti-pattern in the OOP ecosystem—sequential coupling. The process sequence occurs whenever a call to a microservice is dependent on the execution of another call.

This type of behavior is sometimes not an anti-pattern for microservices that work with synchronous calls. However, with respect to the microservices of asynchronous characteristics, it is a mistake of drawing in the communication and domains of microservices.

Unlike sequential coupling, where one class depends on the method of another class, in the case of microservices, the process sequence depends on the end of the processing of a microservice to use data already processed previously in another microservice.

We are not talking about the case where a microservice calls another microservice asynchronously. This is where two microservices are listening to layers in separate queues, but one of them needs to know that the other has...