You're reading from Microservices with Spring Boot 3 and Spring Cloud, Third Edition Build resilient and scalable microservices using Spring Cloud, Istio, and Kubernetes

Product type Paperback

Published in Aug 2023

Publisher Packt

ISBN-13 9781805128694

Length 706 pages

Edition 3rd Edition

Languages

Java

Tools

Istio

Concepts

Microservices

Author (1):

Magnus Larsson AB

View More author details

Table of Contents (26) Chapters

Preface

1. Introduction to Microservices

2. Introduction to Spring Boot FREE CHAPTER

3. Creating a Set of Cooperating Microservices

4. Deploying Our Microservices Using Docker

5. Adding an API Description Using OpenAPI

6. Adding Persistence

7. Developing Reactive Microservices

8. Introduction to Spring Cloud

9. Adding Service Discovery Using Netflix Eureka

10. Using Spring Cloud Gateway to Hide Microservices behind an Edge Server

11. Securing Access to APIs

12. Centralized Configuration

13. Improving Resilience Using Resilience4j

14. Understanding Distributed Tracing

15. Introduction to Kubernetes

16. Deploying Our Microservices to Kubernetes

17. Implementing Kubernetes Features to Simplify the System Landscape

18. Using a Service Mesh to Improve Observability and Management

19. Centralized Logging with the EFK Stack

20. Monitoring Microservices

21. Installation Instructions for macOS

22. Installation Instructions for Microsoft Windows with WSL 2 and Ubuntu

23. Native-Complied Java Microservices

24. Other Books You May Enjoy

25. Index

My way into microservices

When I first learned about the concept of microservices back in 2014, I realized that I had been developing microservices (well, kind of) for a number of years without knowing it was microservices I was dealing with. I was involved in a project that started in 2009 where we developed a platform based on a set of separated features. The platform was delivered to a number of customers that deployed it on-premises. To make it easy for customers to pick and choose what features they wanted to use from the platform, each feature was developed as an autonomous software component; that is, it had its own persistent data and only communicated with other components using well-defined APIs.

Since I can’t discuss specific features in this project’s platform, I have generalized the names of the components, which are labeled from Component A to Component F. The composition of the platform as a set of components is illustrated as follows: