Will my library or framework work on Quarkus (and GraalVM)?
summary
Quarkus runs most libraries and frameworks if porting fixes are applied: use compile-time augmentation and split code into build-time module / deployment suffix plus runtime recorders so bootstrap calls are recorded not executed, scan jars with Jandex to find annotations without loading classes, and explicitly register for reflection, proxies and native resources. Watch out for static initializers (threads, sockets), dynamic classloading, and resources — substitutions or Gizmo bytecode can patch libraries; Camel was successfully ported using these techniques.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:55Overview
- 1:57Quarkus
- 8:00What is Quarkus
- 16:05How Quarkus works
- 21:00Practical example
- 23:20Record methods
- 27:34Extensions
- 32:10Configuration
- 34:48Substitutions
- 36:31Other topics
- 37:34Summary
- 38:39Questions
- 39:45Where is the similarity
- 42:28Spring compatibility layers
