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

Introducing Kubernetes API objects

Kubernetes defines an API that is used to manage different types of objects or resources, as they are also known. Some of the most commonly used types, or kinds, as referred to in the API, are as follows:

Node: A node represents a server, virtual or physical, in the cluster.
Pod: A Pod represents the smallest possible deployable component in Kubernetes, consisting of one or more co-located containers. The containers share the same IP address and port range. This means that containers in the same Pod instance can talk to each other over localhost, but need to be aware of potential port collisions. Typically, a Pod consists of one container, but there are use cases for extending the functionality of the main container by running the second container in a Pod. In Chapter 18, Using a Service Mesh to Improve Observability and Management, a second container will be used in the Pods, running a sidecar that makes the main container join...