Zero Waste, Radical Magic, and Italian Graft – Quarkus Efficiency Secrets
summary
Quarkus shifts heavy work from runtime to build time, using a Jandex offline index and an extensible build steps/build items model so libraries participate in the speedup; JVM mode keeps high throughput while native (GraalVM) starts in tens of milliseconds and keeps a tiny memory footprint. A cache‑pollution bug fix raises measured throughput from about 1.8M to 5.8M req/s; some hot‑path fixes replace idiomatic code (instanceof) with uglier but faster alternatives. Dev mode live coding hides build‑time costs and a Vert.x reactive core remains optional.
AI-written summary · about
chapters (9)
- 0:00The Rust vs Java trade-off
- 3:54Introducing Quarkus
- 8:35Overcoming Java dynamism
- 17:57Build-time processing
- 21:51Developer joy and feedback
- 25:26The power of Jandex
- 34:23Reactive programming
- 36:49Performance engineering
- 47:31Efficiency and sustainability
related talks
50mQuarkus Unleashed
51mQuarkus why, how and what
45mQuarkus Unleashed
48mWhy Quarkus Should Be Your Next Tech Stack: Faster, Greener & Happier
01h 00mQuarkus from inside
45mFaster, greener, and happier- why Quarkus should be your next tech stack
52mQuarkus Supersonic Subatomic Java
42mWill my library or framework work on Quarkus (and GraalVM)?
