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

Unit tests


Unit tests are well-known and are already normative in the software development industry. There are a number of standards and practices for unit tests. However, the best practice for unit tests is to make sure that they are running every software built.

The unit tests are used to prove the smallest testable part of a computer program. In this sense, the great challenge is to write code that is testable; otherwise, it will be impossible to apply the unit tests.

An important feature is that unit tests only prove the code unit segment. Imagine that we are going to test a function that communicates with the database. When we create the unit test, we have to use a mechanism so that the function test does not touch the database. The mechanism is commonly known as a mock. When applying a mock to the unit test, we isolate the function we want to test, then any possible changes in the database will not create conflict in the unit test scenarios.

Unit tests that have factors that can change...