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


The subject of this book talks about communication between microservices. The best way to address this is in a practical way, and we will understand this communication as we develop our orchestrator_news_service microservice.

First, let's understand how we will apply the communication flow. To do this, let's observe the following diagram. The UI makes a request that passes through the Load Balancer and arrives at the NewOrchestrator, which is our microservice responsible for orchestrating the news data. After that, the orchestrator writes in the Message Broker (in our case, a RabbitMQ), a message saying what data types the UI has requested to be orchestrated.

Each News microservice knows exactly what kind of message it is; it is up to you to respond to it. The response process of microservices is very similar to that of the orchestrator, as it also writes a response message to the orchestrator who knows exactly where to read.

This process of exchanging messages is...