Bolt Driver Compatibility Matrix
ArcadeDB’s Neo4j BOLT protocol implementation is certified against every official Neo4j driver — Java, JavaScript, Python, .NET, and Go — driven by a single, language-neutral conformance spec. Every driver is proven against the full feature matrix, and every unsupported cell is an explicitly documented limitation, never a silent omission.
|
The full driver × feature × version matrix is generated from CI and is the authoritative source. It is published and kept current in the ArcadeDB repository:
The matrix on this page summarizes the certified feature areas. Consult the generated matrix above for exact per-version results. |
Certified Feature Areas
| Area | Scenarios | Status |
|---|---|---|
Connection |
|
Certified |
Authentication |
Basic auth (valid / invalid credentials); scheme |
Certified |
Transactions |
Autocommit; explicit |
Certified |
Causal consistency |
Bookmarks (read-after-write across sessions) |
Certified |
Multi-database |
Per-session named-database selection; isolation across databases |
Certified |
Result handling |
Streaming |
Certified |
Type round-trip |
Node, Relationship, Path; temporal ( |
Certified |
Errors |
|
Certified |
Protocol |
BOLT 3.0 / 4.0 / 4.4 and 5.0–5.4 negotiation; |
Certified |
Documented Limitations
These cells are deliberate, documented differences rather than defects:
-
Auth
none— always rejected; ArcadeDB requires credentials. -
Unauthenticated
RUN— the "reject a query before authentication" scenario cannot be exercised through any official driver, because every driver completes the handshake before exposing query methods. It is therefore marked not-applicable rather than tested. -
Heterogeneous HA BOLT ports — clusters whose nodes expose BOLT on different ports must declare each node’s client-reachable address in
arcadedb.ha.serverList(see Routing and High Availability). -
RID/UUID— serialized as strings (no native BOLT type). -
BigDecimal/ oversizedBigInteger— down-converted todouble(possible precision loss).
Certified Drivers and Versions
Each driver is pinned for PR-gating CI and re-tested nightly across a wider version band, so a driver-side release that breaks compatibility is caught quickly. The pinned versions live in the driver-version matrix.
| Language | Driver | Certified version bands |
|---|---|---|
Java |
|
4.4.x (legacy), 5.x, 6.x |
JavaScript |
|
5.x, 6.x |
Python |
|
5.x (LTS), 6.x |
.NET |
|
5.x, 6.x |
Go |
|
5.x |
For the advertised server identity these results are measured against, see Server Identity and Feature Envelope.