Quarkus Unleashed
summary
Quarkus shifts expensive runtime work into compilation so apps start fast and use less memory, achieved by build steps and build items in extension deployment modules that produce and consume metadata, a Jandex class index, and recorders and bytecode generation to serialize expensive objects at build time and recreate them at startup. Demonstrated: a simple extension that precomputes a heavy transformer, and a DataFaker extension that auto-discovers provider classes via the index, hot-reloads YAML data, and applies GraalVM substitutions to fix native-image Random-seed failures so the native build can succeed.
AI-written summary · about
chapters (7)
- 0:00Introduction to Quarkus
- 1:40Quarkus Java optimization
- 10:26Build-time benefits and native image
- 20:20First Quarkus extension
- 28:32Optimizing libraries with extensions
- 34:31Native image limitations
- 44:16Q&A
related talks
45mQuarkus Unleashed
51mQuarkus why, how and what
42mWill my library or framework work on Quarkus (and GraalVM)?
49mQuarkus, the Java Stack back from the Future
01h 00mQuarkus from inside
51mWhy you're missing out if you're not making Quarkus extensions
51mZero Waste, Radical Magic, and Italian Graft – Quarkus Efficiency Secrets
52mQuarkus Supersonic Subatomic Java