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

Pros and cons of the asynchronous messaging design pattern


The asynchronous messaging design pattern is complex to understand initially, but it offers extreme scalability. Understanding the pattern, practicing creating proofs of concept, and choosing the tools well, makes your application have scalability and resilience and reduces the complexity of the pattern.

Some examples of the good points that the pattern offers us are:

  • Independent scalability
  • Extreme scalability
  • Lazy processing
  • Encapsulation of accesses to microservices

However, we must also understand some negative points of the pattern:

  • Complexity in the monitoring of requisitions
  • Complexity of the initial understanding of the pattern
  • Difficulty of debugging

The complexity of the asynchronous messaging design pattern should not serve as a barrier for using the pattern. A good domain design and choosing the tools to work well with are fundamental to the full operation of the microservices that use the pattern. Any initial problems presented...