Skip to content

GraphBridge documentation

GraphBridge: a graph database, no second ORM

GraphBridge is a real Entity Framework Core provider for Neo4j. EF Core owns your model, entity identity and change tracking; the official Neo4j .NET driver owns the connection; GraphBridge maps entities to nodes and relationships and translates queries into parameterized Cypher. It is a developer preview: every supported behavior is tested against a real Neo4j database, and every limit is written down.

Start here

What is GraphBridge The visual introduction: the idea, the storage forms, the query surfaces and the tools (open it on the documentation site)
Concepts The same ideas in words: how EF concepts map to the graph, and the three ways to query
Getting started Install, configure UseNeo4j, map an entity, save it and see the Cypher
Workshop 31 runnable lessons, about three hours for the core track
Samples Five complete applications to copy from

Features

Area Pages
Mapping the graph Mapping nodes · References · Associations · Identified relationships
Querying LINQ queries · Fluent Cypher · Native Cypher · Bounded paths · Graph search · Query inspection
Writing Transactions and concurrency · Bulk mutations · Nulls, types and time
Operating Schema and migrations · Command tracing

Which query surface to use: choosing a level.

Tools

Doctor · Verify · Query Lab · Mapping generator · GraphBridge.Tool · Design-time commands · Project template

None of the tools is needed at runtime. Doctor, Verify and Query Lab only read: they never write to your database.

Reference

Architecture

Overview · Decision records · EF service map

Evidence and contributing

What was tested, and how, lives next to the tests: verification summary, feature evidence, capability evidence, EF conformance matrix and Fluent Cypher acceptance. To build and run the tests, see tests/README and contributing.