Quarkus 3: The Road to Loom for Cheaper, Faster, and Easier Concurrent Applications
summary
Quarkus 3 adds an easy path to Project Loom by letting methods run on virtual threads via a single annotation and JDK preview flags (demonstrated on JDK 20 preview), with demos of three modules: imperative, reactive, and virtual-thread-backed blocking using PostgreSQL + Hibernate ORM Panache and Quarkus DevServices. Benchmarks show virtual threads are cheaper and faster up to about 2,000 concurrency, but slow and use more CPU/RSS past roughly ~3700 concurrency threshold; reactive remains most resource-efficient at high scale.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 3:39Threading model in Java
- 13:54Project Loom overview
- 22:02Quarkus and virtual threads
- 28:26Demo: Non-reactive app
- 36:41Demo: Reactive app
- 38:50Demo: Virtual threads
- 45:15Benchmark results
- 48:45Key takeaways and roadmap
related talks
50mQuarkus 3: The Road to Loom for Cheaper, Faster, and Easier Concurrent Applications
51mQuarkus 3: Elevating Java Microservices with Project Loom and Beyond
51mQuarkus why, how and what
01h 56mConcurrency Crossroads: Choosing between Reactive Programming & Virtual Threads
49mQuarkus, the Java Stack back from the Future
57mJDK 19 Virtual Threads: Skip Reactive, Boost Throughput
41mServices Reloaded Increased Throughput with Project Loom Virtual Threads
50mVirtual threads - no pain, no gain