Java Project Loom: Why Should I Care?
summary
Project Loom adds virtual threads plus structured concurrency and shows concrete results: four demo apps (blocking Spring Boot, reactive WebFlux, Spring Boot on virtual threads, Helidon Nima) run against a 1s-delay backend and the blocking Spring app handles about ~200 req/s with average latency ballooning to ~5s while reactive and virtual-thread variants deliver ~1000 req/s and ~1s latency. Requires Java 19 preview to experiment or Java 21 for GA; replace synchronized blocks with ReentrantLock, watch thread‑locals (use ScopedValues) and enable a virtual-thread executor in Spring Boot 3.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:19What?
- 0:42Why?
- 1:16The problem
- 2:35Possible solutions
- 3:22Answer: Virtual threads
- 5:47Existing solutions
- 11:21Virtual threads
- 13:24Architecture
- 15:16Demo
- 16:15Results
- 17:04Conclusion
- 19:56Demo
- 21:58Thread pinning
- 24:14Demo
- 26:20ScopedValue
- 27:20Demo
- 28:15Structured concurrency
- 29:46Demo
- 31:42Loom
- 32:09Want to get started now?
- 33:33Is reactive dead?
- 34:28What about Kotlin coroutines?
- 35:57Conclusion
- 37:05Outro
related talks
47mConcurrent and Asynchronous Programming: Loom in Java 20 and 21
49mPrepare for what “Loom”s ahead.
31mJava Virtual Threads
51mWhat's Looming in Java The Why and What of Project Loom
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
36mPreparing web applications for Loom
46mJava 21: The Revolution of Virtual Threads - A Deep Dive
46mJava 21: The revolution of virtual threads - A Deep dive