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

Consolidating responses


The shared data pattern does not address any kind of consolidation of reply, because this is a pattern with the focus on storage. However, we need to access our microservices. To do that, we'll modify some of our Nginx configurations.

We'll totally modify the instances of upstream configuration. As you can see, we modified the upstream name and added more server instances to the direction of our microservices. In this setting, each microservice has four instances:

 
  upstream proxy_servers { 
        server bookproject_userservice_1:3000; 
        server bookproject_userservice_2:3000; 
        server bookproject_userservice_3:3000; 
        server bookproject_userservice_4:3000; 
        server bookproject_famous_news_service_1:5000; 
        server bookproject_famous_news_service_2:5000; 
        server bookproject_famous_news_service_3:5000; 
        server bookproject_famous_news_service_4:5000; 
        server bookproject_politics_news_service_1:5000; 
      ...