Phil Clay at SpringOne 2020
summary
Blizzard moves Java services to Project Reactor to make global account flows responsive, pre-assembling publishers that defer I/O until subscription and using Mono and Flux for composition and backpressure. Reactive libraries replace futures and callbacks with WebFlux, Reactor Netty and Reactor RabbitMQ, plus reactive OAuth and observability hooks so metrics and tracing work end-to-end. Debugging uses the Reactor debug agent, IntelliJ inspections and async profilers. Advice: adopt reactive selectively for high‑throughput, async paths.
AI-written summary · about
related talks
24mBringing Reactive Programming to Java and Microservices
47mReactive Spring
53mRefactor to Reactive with Spring 5 and Project Reactor
56mKEYNOTE - Designing Applications: The Reactive Way
57mRefactor to Reactive with Spring 5 and Reactor 3
49mReactive Spring
41mThe definite guide to reactive programming in Java
41mFrom Imperative To Reactive