5 ways to improve your Java EE applications in reactive way
summary
Claims five incremental, non‑rewriting ways to make Java EE apps more responsive under load, applied to a production‑like cargo tracker and measured for latency and user experience. Uses Java EE and Java 8 primitives (CompletableFuture, JAX‑RS async/rx) to build an async pipeline with CompletableFuture and JAX‑RS async/rx, moves updates via WebSockets and CDI events, isolates blocking work on separate executors, handles context/transaction propagation, and reports concrete before/after performance and UX improvements.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:09About me
- 1:23Overview
- 3:09What happens
- 3:22The problem
- 4:44The problems
- 6:01Reactive Manifesto
- 7:52Thread starvation
- 9:43Reusing threats
- 10:46Responsive messages
- 12:22Synchronous API
- 13:22Missing Synchronous API
- 15:09Example
- 16:06Immediate response
- 17:26Cargo Traffic Tracker
- 18:12Administration Interface
- 18:28Default State
- 19:25WebSocket
- 21:03Synchronous Pipeline
- 23:56RX
- 25:02Java EE 8
- 27:21Messages
- 30:52Service Events
- 35:35Isolation
- 38:43CDI events
- 42:29Graph travels
- 45:00Computable future
- 47:46Contact propagation
- 49:59Solutions
- 51:25Summary
related talks
40mReactive programming: lessons learned
40mREACTIVE A New Hope! Learn From a Performance History
46mGet Reactive! Programming, Systems, and Microservices
15mReactifying your application
50mThe State of Server Side Java Webapps
54mReactive for CRUD: fantasies and reality
42mReacting to the Future of Application Architecture
45mReactive web services