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

Circuit breaker


The circuit breaker is an automatic operating switch that turns itself off when there is an overload or short circuit. As well as the electric fuse, the purpose of the circuit breaker is failing quickly and protecting electrical installations. In the case of a microservice, it protects the general integrity of the application.

Imagine the situation where a microservice presents slowness. The requests keep coming, and it begins to be queued. At some point, collateral damage happens. Especially in the case of a microservice that has a dependency on communication with other microservices, we need to apply the circuit breaker.

The concept of the circuit breaker is relatively simple, possessed by only two states:

  • On: Releasing the call to the external dependency
  • Off: Failing the call immediately and taking a previously configured action

In practice, instead of microservices directly accessing the external dependency, the circuit breaker will put itself in the middle of the call. In...