8 Reactive Spring: Resilience and scalability

Polarsophia, the organization behind the Polar Bookshop business, is very happy with the progress of its new software product. Its mission is to spread knowledge and awareness about the North Pole and the Arctic, and making its book catalog available worldwide is an essential part of this.

The Catalog Service application you built so far is a good starting point. It fulfills the requirements of browsing and managing books, and it does that while following cloud native patterns and practices. It’s self-contained and stateless. It uses a database as a backing service to store the state. It can be configured externally through environment variables or a configuration server. It respects environment parity. It’s verified through the automated execution of tests as part of a deployment pipeline, following continuous delivery practices. For maximum portability, it’s also containerized and can be deployed to a Kubernetes cluster using native functionality like service discovery, load balancing, and replication.

8.1 Asynchronous and non-blocking architectures with Reactor and Spring

8.1.1 From thread-per-request to event loop

8.1.2 Project Reactor: Reactive streams with Mono and Flux

8.1.3 Understanding the Spring reactive stack

8.2 Reactive servers with Spring WebFlux and Spring Data R2DBC

8.2.1 Bootstrapping a reactive application with Spring Boot

8.2.2 Persisting data reactively with Spring Data R2DBC

8.2.3 Implementing the business logic with reactive streams

8.2.4 Exposing a REST API with Spring WebFlux

8.3 Reactive clients with Spring WebClient

8.3.1 Service-to-service communication in Spring

8.3.2 Understanding how to exchange data

8.3.3 Implementing REST clients with WebClient