Quarkus, Helidon, Micronaut

Important - page not maintained

This page is no longer being maintained and its content may be out of date. For the latest guidance, please visit the Getting Started Manual .

For Java developers who use Quarkus, Helidon or Micronaut and want to take advantage of a pre-configured Java driver instance. This page should give an overview of the existing support for the driver in other Java frameworks. Please consult the linked documentations for more information.


Driver integration

The goal with all three integrations is to provide support for getting a managed instances of the Neo4j driver. Like in the Spring Framework, you can provide the driver properties to an application.properties file (or yaml) to configure your application. In the end you will have an injectable driver instance that can be used with

Driver driver;

in the business operation code base.

Additional to the managed driver bean creation, the integrations also expose health metrics for the driver and connection to your Neo4j instance.


In an existing Quarkus application you need to add the quarkus-neo4j dependency to your project.


Additionally configure the basic connection parameters as needed.

Quarkus application.properties
quarkus.neo4j.uri = bolt://localhost:7687
quarkus.neo4j.authentication.username = neo4j
quarkus.neo4j.authentication.password = secret

If you want to make use of the health check, the additional quarkus-smallrye-health dependency is needed.


For metrics support, you would either need MicroMeter (recommended by Quarkus) or SmallRye Metrics (only if you really need MicroProfile specification) dependencies declared.

MicroMeter (Prometheus) dependency

The metrics for Neo4j have to be manually enabled in the application.properties.

quarkus.neo4j.pool.metrics-enabled = true


In a Helidon-based application you need to declare the Neo4j Java driver dependency in your Maven pom.xml.


Providing the essential connection parameters will give you a managed instance of the Java driver.

Helidon application.properties
neo4j.uri = bolt://localhost:7687
neo4j.authentication.username = neo4j
neo4j.authentication.password = secret
# Enable metrics
neo4j.pool.metricsEnabled = true

If you want to use the health and metrics system, you have to also declare those dependencies provided by the Helidon framework.


Now you can put together the configuration

Configuration with metrics and health
Neo4JSupport neo4j = Neo4JSupport.builder()


and get the managed driver bean.


To enable the Neo4j Driver support in Micronaut, the micronaut-neo4j-bolt dependency needs to get declared.


Adding the needed connection parameters to the application.properties.

Micronaut application.properties
neo4j.uri = bolt://localhost:7687
neo4j.username = neo4j
neo4j.password = secret

The module will automatically add its information to the built-in /health endpoint.


Quarkus Documentation

Neo4j integration, Configuration properties, Guide

Helidon Documentation

Reference, Helidon Neo4j

Micronaut Documentation

Neo4j integration, Guide


Quarkus, Helidon, Micronaut examples