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

Developing the structure


In the previous chapters, we defined our domains, which are as follows:

  • SportNewsService
  • PoliticsNewsService
  • FamousNewsService
  • RecomendationService
  • UsersService

The first step is to choose a domain to apply our techniques. To do this, we will use the UsersService. This domain is quite interesting because it has unique characteristics and is an excellent case to apply the techniques learned here.

Let's gather the tools that we will use for the composition of UsersService. At first, we will use only one database table, but we know that the rest will be created.

Database

Our database is a PostgreSQL and the structure of the first table is extremely simple, as seen in the following screenshot:

In the table users, we have an ID that is the unique identification key, username, user email, and user password.

Programming language and tools

Our UsersService will be written in Go; the tools we use in this programming language have already been described in Chapter 2, The Microservice...