Book Image

Hands-On Microservices with Spring Boot and Spring Cloud

By : Magnus Larsson
Book Image

Hands-On Microservices with Spring Boot and Spring Cloud

By: Magnus Larsson

Overview of this book

Microservices architecture allows developers to build and maintain applications with ease, and enterprises are rapidly adopting it to build software using Spring Boot as their default framework. With this book, you’ll learn how to efficiently build and deploy microservices using Spring Boot. This microservices book will take you through tried and tested approaches to building distributed systems and implementing microservices architecture in your organization. Starting with a set of simple cooperating microservices developed using Spring Boot, you’ll learn how you can add functionalities such as persistence, make your microservices reactive, and describe their APIs using Swagger/OpenAPI. As you advance, you’ll understand how to add different services from Spring Cloud to your microservice system. The book also demonstrates how to deploy your microservices using Kubernetes and manage them with Istio for improved security and traffic management. Finally, you’ll explore centralized log management using the EFK stack and monitor microservices using Prometheus and Grafana. By the end of this book, you’ll be able to build microservices that are scalable and robust using Spring Boot and Spring Cloud.
Table of Contents (26 chapters)
Title Page

Using the persistence layer in the service layer

In this section, we will learn how to use the persistence layer in the service layer to store data and retrieve data from a database. We will go through the following steps:

  1. Log the database connection URL.
  2. Add new APIs.
  3. Use the persistence layer.
  4. Declare a Java bean mapper.
  5. Update the service tests.

Log the database connection URL

When scaling up the number of microservices where each microservice connects to its own database, I find myself, from time to time, in a situation where I'm not sure what database each microservice actually uses. Therefore, I usually add a log statement directly after the startup of a microservice that logs the connection URL that is used to connect...