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

Microservice communication


Like in the chained design pattern, the branch design pattern uses the synchronous communication model between microservices. However, some ways to perform synchronous communication can be exploited.

The first of these is synchronous communication using some protocol or direct message. This is the simplest way to apply synchronous communication between microservices. As an example of protocol, there is the famous HTTP, and as a direct message, we can use Remote Procedure Call (RPC). However, the branch design pattern has a peculiarity—the pattern works with both orchestration and data composition.

In terms of data composition, the use of protocols is quite simple and acceptable. Differently, when we speak of orchestration, we cannot treat it in the same way because the orchestration of data occurs within the same microservice. Having said that, internal communication within a microservice can be worked on in the following three ways:

  • Sequential: No concurrency or...