How to bake reactive behavior into your Java EE applications

on YouTube ↗38m

" summary

Adapts the Cargo Tracker example by splitting route calculation into a REST microservice and streaming incremental route results back to the UI via WebSocket; the client uses JAX‑RS async calls wrapped in CompletableFuture and managed executors to avoid blocking request threads. Runs on Payara Micro with Hazelcast-backed distributed cache and CDI outbound events to broadcast work across nodes. Notes: JDBC stays blocking so use a separate thread pool, and practical issues—timeouts, retries and debugging callbacks—require explicit handling.

AI-written summary · about

" chapters (12)

1. 0:00Introduction and setup
2. 1:14What is reactive programming
3. 7:02Traditional vs reactive apps
4. 10:52Blocking threads and waste
5. 15:30Java EE async APIs
6. 17:38CompletableFuture basics
7. 21:45Context service in Java EE
8. 23:13Demo app: Cargo Tracker
9. 25:22MicroProfile for reactive apps
10. 29:22Async REST and WebSockets
11. 33:49Challenges of reactive programming
12. 35:13Q&A on resilience and error handling

" related talks

• 01h 07mThe Java EE-stic Way of CodingAdam Bien · Jfokus 2016
• 52mBulletproof Java Enterprise Applications for The Hard Production LifeSebastian Daschner · Voxxed Days CERN 2019
• 52mJAX-RS and CDI Bike the Reactive Bridge!David Delabassee, José Paumard · Devoxx Belgium 2017
• 55m10 strategies for developing reliable Jakarta EE & MicroProfile apps for the CloudFabio Turizo · Devnexus 2020
• 01h 01mReactive web servicesKamil Szymański · Build Stuff 2017
• 38mBest Practices in Reactive Application with Java 1.8 and PlayWill Sargent · Devoxx US 2017
• 43mMigrating from Imperative to ReactiveNicolas Fränkel · Conf42 Enterprise Software 2021
• 01h 00mBulletproof Java Enterprise applications for the hard production lifeSebastian Daschner · JPoint 2019