Quarkus 3: The Road to Loom for Cheaper, Faster, and Easier Concurrent Applications
summary
Quarkus 3 runs virtual threads from Java 21 using an easy annotation like @RunOnVirtualThread and demos a Quarkus app backed by an auto-starting PostgreSQL testcontainer and JPA/Hibernate 6. The demo fires 2,000 concurrent transactions (fraud detection) and shows virtual threads are cheap and fast but start degrading around 35k concurrency due to pinning (synchronized/native calls), monopolization (long CPU tasks), thread-safety issues and immature libraries — Quarkus patches and updated Jackson fixes reduce but don’t eliminate gaps.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:04Quarkus and Java 21 overview
- 3:15Java thread models history
- 5:50Blocking vs reactive programming
- 14:46Virtual threads introduction
- 20:08Virtual threads in Quarkus
- 24:47Live demo setup
- 28:08Imperative Quarkus app demo
- 31:01Reactive Quarkus app demo
- 33:08Virtual thread Quarkus app demo
- 35:39Virtual threads in fraud detection
- 36:22Virtual threads limitations and tips
- 43:25Performance comparison
- 45:09Key takeaways and conclusion
- 47:20Q&A session
related talks
51mQuarkus 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
46mQuarkus why, how and what
52mQuarkus Supersonic Subatomic Java
49mQuarkus, the Java Stack back from the Future
48mSupersonic, Subatomic Java with Quarkus
55mWhy You Want to Code With Quarkus in 2023