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

Performing a rolling upgrade

Historically, updates often result in some downtime of the component that is updated. In a system landscape with an increasing number of autonomous microservices that are updated independently of each other, recurring downtimes due to frequent updates of the microservices is not acceptable. Being able to deploy an update without downtime becomes crucial.

In this section, we will see how we can perform a rolling upgrade, updating a microservice to a new version of its Docker image without requiring any downtime. Performing a rolling upgrade means that Kubernetes first starts the new version of the microservice in a new pod, and when it reports as being healthy, Kubernetes will terminate the old one. This ensures that there is always a pod up and running, ready to serve incoming requests during the upgrade. A prerequisite for a rolling upgrade to work...