Neo4j
futomaki.neo4j
A Docker Compose file for Neo4j alone, generated from the catalog and checked by the safety inspector. No account needed.
Graph database built on the property graph model and the Cypher query language, used for knowledge graphs, network analysis and relationship-heavy queries that join badly in SQL.
Neo4j stores nodes and relationships as first-class records with properties on both, so following a relationship is a pointer traversal rather than a join, which keeps deep path queries tractable as the graph grows. Cypher describes patterns declaratively, and the graph data science library adds centrality, community detection and similarity algorithms operating over projected subgraphs. The bundled browser provides a query console and a visual result view. The Community Edition used here runs a single database per instance; clustering, role-based access control and hot backup are Enterprise features.
You know it worked when
- The browser interface loads and authenticates.
- A Cypher query creates nodes and a relationship between them.
- A pattern match returns that relationship.
- A driver connects over Bolt from outside the container and runs the same query.
- The graph is intact after a container restart with a persisted data directory.
Known sharp edges
- Initial credentials are applied only on first start; if the data volume already exists the environment variable is ignored and the previous password stands.
- Heap and page cache default low relative to most graphs and must be tuned, or large traversals fail on memory rather than merely running slowly.
- The Community Edition has no role-based access control and permits one database per instance, so every authenticated user is effectively an administrator.
- Drivers connect over Bolt on a different port from the browser, and exposing only the browser port leaves applications unable to connect.