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

Trying out the edge server

To try out the edge server, we perform the following steps:

  1. First, build the Docker images with the following commands:
cd $BOOK_HOME/Chapter10
./gradlew build && docker-compose build
  1. Next, start the system landscape in Docker and run the usual tests with the following command:
./test-em-all.bash start

Expect output similar to what we have seen in previous chapters:

With the system landscape including the edge server, let's explore the following topics:

  • Examine what is exposed by the edge server outside of the system landscape running in the Docker engine. 
  • Try out some of the most frequently used routing rules as follows:
    • Use URL-based routing to call our APIs through the edge server.
    • Use URL-based routing to call Netflix Eureka through the edge server, both using its API and web-based UI.
    • Use header-based routing to see...