Connecting Java Applications over HTTP to Query API
summary
A preview Java driver module translates run and pull Bolt messages into POSTs to /db/{db}/query/v2, buffers returned records in memory, and honors Neo4j cluster affinity headers so transactions route correctly; it supports three token types, does not do home-database resolution, and is distributed via a driver bill of materials with an optional HTTP runtime module. Demos use plain Java, Spring Data Neo4j and JDBC with Prometheus/Grafana traces and switching only requires flipping the URI to the HTTP port and adding the module.
AI-written summary · about
chapters (11)
- 0:00Introduction and presenters
- 1:13Query API overview
- 3:43Query API live demo
- 6:12Why use HTTP for connections
- 8:40Java driver options
- 11:30HTTP driver implementation
- 13:37New driver module preview
- 16:23Java driver demo setup
- 19:58Spring Data demo
- 24:25JDBC driver demo
- 28:42Flexibility and feedback
related talks
29mNeo4j for Java Developers
31mPouring Coffee into the Matrix - Building Java Apps on Neo4j
31mJDBC, What Is It Good For?
01h 34mSpring Data Daily Double - Couchbase and Neo4J
14mDemystifying Neo4j With APOC and Java
51mEmpowering Enterprise Architectures with Polyglot Persistence
50mBuilding GraphQL APIs with Java
32mIntroducing Neo4j SDN/RX