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

Deployment


We have the application working and we understand how security items work for microservices. Now, let's understand the patterns of deployment, thinking about the microservices architecture.

Continuous integration/continuous delivery/continuous deploy

Continuous integration is a practice where developers merge their changes back into the main branch as often as possible. Developer changes are validated by creating a compilation and running automated tests against the build. When performing the process of continuous integration, the problem that usually occurs when developers wait for the release of a new feature to merge their changes in the launch branch is avoided.

Continuous integration places great emphasis on automated testing to check whether a new feature is in trouble when new commits are being integrated into the core business.

Continuous delivery is an extension of continuous integration to ensure that you can quickly release new features to your customers in an agile and...