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

Best practices


The asynchronous messaging design pattern is a pattern with a high level of complexity for understanding, while having great scalability.

For this pattern, it is fundamental to adopt best practices to make it easy for us to understand the structure of asynchronous messages.

Application definition

Applying the asynchronous messaging design pattern is very healthy for applications, but it is necessary to think of the application as a whole to reach as many microservices as possible using the pattern appropriately.

Often, a micro vision is required to work with other microservices, which is why DDD strength is so important. But sometimes, it is fundamentally a macro view of things making it possible to understand all the communication points of the application and where asynchronism is possible, and moreover, where synchronized communication is unnecessary.

Often, we hope to offer a complete response in the interaction of microservices but, in fact, this may not be necessary. If the...