Will my library or framework work on Quarkus (and GraalVM)?
summary
Quarkus achieves fast boot and low memory by compile time augmentation, generating build-time classes and producing both a JVM mode and a GraalVM native image with the closed‑world assumption; native builds can take minutes but produce tiny executables (example ~12 MB). Extensions split into -deployment (build steps producing/consuming build items) and runtime modules; common tools and fixes include jandex for annotation indexing, explicit reflection/proxy/resource registration, recorder classes with static-init vs runtime-init, and substitutions for problematic libraries (e.g., porting Apache Camel’s ~300 connectors).
AI-written summary · about
chapters (17)
- 0:00Start
- 0:04Maven Demon
- 0:57Porting Libraries and Frameworks to Quarkus
- 3:50Why Would We Want To Use Qualco
- 4:24Dev Mode
- 5:09Dev Services
- 6:09Continuous Testing
- 8:44Extensions
- 10:09Third-Party Frameworks
- 11:59How Quakus Works
- 13:08Modes of Operations
- 14:52Limitations
- 17:14Class Initializers
- 23:40Quarkus Build Time Container
- 30:46Camera Context
- 35:56Extension Configurations
- 42:08Useful Links
related talks
49mWill my library or framework work on Quarkus (and GraalVM)?
45mQuarkus Unleashed
01h 00mQuarkus from inside
11mAll about Quarkus
50mQuarkus Unleashed
51mQuarkus and GraalVM: booting Hibernate at supersonic speed, subatomic size
51mQuarkus why, how and what
42mLess waste, more joy, and a lot more green: How Quarkus makes Java better