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

Proxy strategy to orchestrator


The proxy design pattern does not have an elaborated strategy for data orchestration. As already discussed earlier in this chapter, the proxy performs tasks only at the request level. Of course, some information from a request may receive special treatment, but it does not compare to what we saw in the orchestrator design pattern.

When we talk about data orchestration using the proxy design pattern, we are looking directly at the request. The approach using proxy does not preclude the adoption of another pattern for microservices; sometimes, it is of great help to migrate monolithic to microservices.

Imagine that we have a monolithic application that we want to decompose and move its domains to microservices. The initiative is commendable, but we cannot stop developing new features while we are shutting down the monolithic application. Soon, the strategy will be to use the proxy design pattern to keep the application working, while we move the business and apply...