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

Monitoring microservices


Some microservices fail to come into production due to lack of monitoring. Even with tests in controlled environments, it is very difficult to get a true picture of a microservice's performance. The production numbers will give us a final view of the scalability, availability, and performance of an application.

Not having alert systems and constantly collecting metrics from the microservices can cause a higher number of hits, override the application, or cause some instability in some segments of the system. Unmonitored instability is the most dangerous case because it is a silent error and difficult to detect; it will probably be too late by the time we find it.

In some cases, microservice instabilities happen because the development team did not understand the monitoring metrics of the application or did not know how to properly collect them.

Monitoring a single service

Application monitoring, in general, seems simple. However, it implies a great capacity for analysis...