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

Fail strategies


We saw a number of anti-patterns in the process of developing our application. However, among all the collateral damage that can be generated by anti-patterns, the most harmful for an application that uses the microservices architecture is the cyclic call between microservices.

Cyclic calls prevent continuous integration, independent deployment, and progressive evolution of each microservice and create a false sense of success in tests. A good example of this kind of failure is if we removed NewsOrchestrator and passed the orchestration responsibility to one of the internal layer microservices. A microservice would have the domain corrupted, in addition to generating the need to deploy with other parts of the application at the same time.

The proper adoption of the patterns acts to prevent this type of failure in the strategy of microservices.

Obviously, techniques such as circuit breaker and timeout, as explained in Chapter 4, Microsystem Ecosystem, are welcome whenever we...