How Quarkus operates with GraalVM demonstrated with Neo4j
summary
Quarkus extensions and GraalVM native-image are used to run the Neo4j Java driver and OGM natively, with build-time augmentation that generates bytecode, records runtime initialization, and opens JDBC-like connections during build. The demo shows agent-produced reflection configs and measurable tradeoffs: native images take tens of seconds to compile but start fast; observed results include native-image agent generated reflect-config, 7s cold startup including Neo4j container, 140 MB JavaScript native image; SSL integration proves workable and ~500 lines of driver glue are removed.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:08Two execution modes
- 6:59Build-Time- and Runtime-Initialization
- 22:07Different solutions
- 24:29Structure and flow of a Quarkus-Extension
- 36:59The relevance to the ecosystem
related talks
45mQuarkus Unleashed
42mWill my library or framework work on Quarkus (and GraalVM)?
51mQuarkus and GraalVM: booting Hibernate at supersonic speed, subatomic size
52mQuarkus Supersonic Subatomic Java
42mLess waste, more joy, and a lot more green: How Quarkus makes Java better
49mJava Particle Acceleration using Quarkus
56mMaximizing Performance with GraalVM
42mJava in the Cloud with GraalVM