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

Chapter 4. Microservice Ecosystem

There are some things we don't know when we write software. For example, whether the software will be a success or not. However, some things will not be right when we write an application and put it into production; there will be failures.

Someone, at some point, said that there can be no software without bugs; at best, the software may have an unknown bug. Unfortunately, this statement is true; we could say that it's a phrase that is almost 100% accurate.

Often, the applications that we write have high test coverage; the domain business also features automated tests and all the integrations as well. Apparently, everything is fine. However, when we talk about microservices, we should add a few potential risk points, for example, network connection, errors in the load balance, and faults in the external service consumption.

Okay, our microservices, at some point, will fail, either due to a bug introduced by the development team or as a result of integration...