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

Data definition – RecommendationService


Let's begin the technical development of our RecommendationService microservice by creating a container with the database that will be used. In the case of our microservices, we will use a database based on graphs—the Neo4j. The behavior of this database is very interesting, besides being easy to implement, thus being a perfect example for our application.

In our docker-compose.yml file, we make a small change by adding Neo4j to our stack:

    recommendation_db:
      image: neo4j:latest
      ports:
        - "7474:7474"
        - "7687:7687"
      environment:
        NEO4J_AUTH: "none"

With this simple particle of code, we already have an instance of Neo4j inside a Docker container.