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

Communication layer and accreditation between services


Currently, the communication between microservices has the following model of calls:

As you can see, we use RPC and PUB/SUB for the internal layer and HTTP calls for calls made in the public-facing layer. At one point in our internal layer, we make use of the HTTP protocol. There is nothing wrong with this, but RPC for calls between microservices is the most efficient, especially if we use some kind of data wrapper, such as binary protocol or some other mechanism for packet reduction.

Let's modify this call to an RPC. However, it will be different from the RPCs we currently have, since we will pass a binary protocol package. For this, we will use the gRPC, creating a server in UsersService and a client in RecommendationService.

This HTTP call that we want to delete is in RecommendationService, in the receiver method of the Recommendation class, inside the service.py file, as you can see here:

    ...
       def receiver(self, data):
   ...