I’m gonna first speak briefly about Neo4j itself, what’s the core product and why you might interested in it.
Give you an idea about my background (while this is often irrelevant or marketing, it may be of interest in the context of Quarkus)
Praise the Java community, which despite some other rumors manages to work closely together with great benefit for the whole ecosystem
We will than have a look at the building blocks of a Quarkus extension as well as the Neo4j database drivers
Quarkus calls itself „Supersonic subatomic Java“ and „a Kubernetes Native Java stack tailored for OpenJDK HotSpot and GraalVM“, meaning that applications build with it should be able to use GraalVM’s native-image tool to produce binary running GraalVMs SubstrateVM. For us this required changes to our Java driver which I would like to discuss as well.
And last but not least, I want to show you the resulting pieces in action