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

Preparing the containers for the integration test


Before we really talk about the integration test, let's prepare our containers for testing. We use docker-compose in our development environment, but currently, all of our application settings are in the same docker-compose.yml file.

docker-compose allows us to override settings by passing docker-compose.yml files into jail, as shown in the following example:

$  docker-compose -f docker-compose.yml -f docker-compose.test.yml up --build –d

Let's separate the settings and create different docker-compose files. Each file will be for a specific environment. We will create a new file, docker-compose.test.yml. This file has only the settings that we want to overwrite:

version: '3'
services:
  users_service:
    environment:
      - DATABASE_URL=postgresql://postgres:postgres@users_service_db:5432/users_test?sslmode=disable

  famous_news_service:
    environment:
      - QUERYBD_HOST=mongodb://querydb_famous:27017/news_test
      - COMMANDDB_HOST=postgresql...