Quarkus meets Neo4j - Speaker Deck

Slide 1

Slide 1 text

About writing a natively compilable Quarkus extension Michael Simons, @rotnroll666 Quarkus meets Neo4j

Slide 2

Slide 2 text

Quarkus meets Neo4j by @rotnroll666 • About Neo4j • About me and Quarkus • Building blocks of… • … the Neo4j database driver • … a Quarkus extension • The search for the holy Graal(VM): AoT compiling a database driver. 2 Agenda

Slide 3

Slide 3 text

About Neo4j

Slide 4

Slide 4 text

Ecosystem Neo4j Professional Services 300+ partners 47,000 group members 61,000 trained engineers 3.5M downloads Mindset “Graph Thinking” is all about considering connections in data as important as the data itself. Native Graph Platform Neo4j is an internet-scale, native graph database which executes connected workloads faster than any other database management system. Neo4j 4

Slide 5

Slide 5 text

The whiteboard model IS the physical model • Bands are founded in and solo artists are born in countries • Sometimes Artists are associated with other Artists and bands have member • Artists used to release Albums :Artist :Band :SoloArtist :Country :FOUNDED_IN :BORN_IN :ASSOCIATED_WITH :HAS_MEMBER :Album :RELEASED_BY 5

Slide 6

Slide 6 text

Querying with Cypher • Cypher is to Neo4j what SQL is to RDBMS: A declarative, powerful query language • https://www.opencypher.org / The GQL Manifesto MATCH (a:Album) -[:RELEASED_BY]-# (b:Band), (c) $-[:FOUNDED_IN]- (b) -[:HAS_MEMBER]-# (m) -[:BORN_IN]-# (c2) WHERE a.name = 'Innuendo' RETURN b, m, c, c2 6

Slide 7

Slide 7 text

About me and Quarkus

Slide 8

Slide 8 text

Quarkus meets Neo4j by @rotnroll666 • Neo4j since July 2018 • Java Champion • Co-Founder and current lead of Java User Group EuregJUG • Author (Spring Boot 2 und Arc42 by example) About me 8 First contact to Neo4j through

Slide 9

Slide 9 text

Quarkus meets Neo4j by @rotnroll666 Graph Tour 2019 9 Now online: https://neo4j.com/graphtour/

Slide 10

Slide 10 text

Quarkus meets Neo4j by @rotnroll666 Graph Tour 2019 9 Now online: https://neo4j.com/graphtour/

Slide 11

Slide 11 text

Quarkus meets Neo4j by @rotnroll666 A Hibernate team lead appears… 10 With Sanne Grinovero, Hibernate Team Lead & Quarkus R&D

Slide 12

Slide 12 text

Building blocks

Slide 13

Slide 13 text

Quarkus meets Neo4j by @rotnroll666 12 The Neo4j Java-Driver org.neo4j.driver#$groupId> neo4j-java-driver#$artifactId> 4.1.1#$version> #$dependency> var driver = GraphDatabase.driver( "bolt:#%localhost:7687", AuthTokens.basic("neo4j", "secret"), Config.builder().withLogging(Logging.console(Level.INFO)).build() );

Slide 14

Slide 14 text

Quarkus meets Neo4j by @rotnroll666 13 Imperative sessions Function getNameFromRecord = record #& record.get("name").asString(); try (var session = driver.session()) { var names = session.readTransaction( tx #& tx .run("MATCH (n:Artist) RETURN n.name AS name") .stream().map(getNameFromRecord) .collect(toList()) ); names.forEach(System.out#'println); }

Slide 15

Slide 15 text

Quarkus meets Neo4j by @rotnroll666 14 Reactive sessions with Project Reactor Function getNameFromRecord = record #& record.get("name").asString(); RxTransactionWork

Slide 16

Slide 16 text

Quarkus meets Neo4j by @rotnroll666 15 Reactive sessions with SmallRye Mutiny Function getNameFromRecord = record #& record.get("name").asString(); RxTransactionWork

Slide 17

Slide 17 text

Quarkus meets Neo4j by @rotnroll666 16 The Quarkus extension system var driver = GraphDatabase.driver( "bolt:#%localhost:7687", AuthTokens.basic("neo4j", "secret"), Config.builder().withLogging(Logging.console(Level.INFO)).build() );

Slide 18

Slide 18 text

Quarkus meets Neo4j by @rotnroll666 16 The Quarkus extension system quarkus.neo4j.uri = bolt:#%localhost:7687 quarkus.neo4j.authentication.username = neo4j quarkus.neo4j.authentication.password = secret @Path("/hello") public class ExampleResource { private final Driver driver; @Inject public ExampleResource(Driver driver) { this.driver = driver; } }

Slide 19

Slide 19 text

Quarkus meets Neo4j by @rotnroll666 • The runtime module which represents the capabilities the extension developer exposes to the application’s developer • The deployment module which is used during the augmentation phase of the build, it describes how to "deploy" a library following the Quarkus philosophy The deployment module often depends on the runtime module. 17 The Quarkus extension system A Quarkus extension consists of two parts:

Slide 20

Slide 20 text

Quarkus meets Neo4j by @rotnroll666 • GraalVM restrictions • Dynamic class loading (Classes must be enumerated) • Reﬂection (Must be enumerated, too) • JCA (Java Cryptography Architecture) needs special treatment • Optimizing things (i.e. Replacing Service Loader with an index) • @BuildStep’s record byte code with @Recorder’s 18 The Quarkus extension system Three phases of bootstrapping: 1. Augmentation via build step processors

Slide 21

Slide 21 text

Quarkus meets Neo4j by @rotnroll666 •@Record(STATIC_INIT) • Will run in a static init method on the main class during native build • Executed on the standard JVM during build • Objects will be directly serialized into the native executable 19 The Quarkus extension system Three phases of bootstrapping: 2. Static init

Slide 22

Slide 22 text

Quarkus meets Neo4j by @rotnroll666 •@Record(RUNTIME_INIT) • Will run from the applications main method during native boot 20 The Quarkus extension system Three phases of bootstrapping: 3. Runtime init