Memgraph
futomaki.memgraph
A Docker Compose file for Memgraph alone, generated from the catalog and checked by the safety inspector. No account needed.
In-memory graph database speaking Cypher, built for graphs that change constantly — streaming updates, real-time traversals and analytics over relationships as they form.
Memgraph holds the graph in memory rather than paging it from disk, which makes deep traversals and pattern matches fast enough to sit inside a request path, with durability provided by periodic snapshots and a write-ahead log. It implements Cypher and is broadly compatible with Neo4j's dialect and the Bolt protocol, so existing drivers and many existing queries transfer. Streaming connectors consume from Kafka and similar sources to keep the graph current, and the MAGE library adds graph algorithms callable from within a query. The platform image bundles the database with the Lab interface and console.
You know it worked when
- The database accepts a Bolt connection from a client.
- Nodes and relationships created by a Cypher query can be read back.
- A multi-hop traversal returns the expected paths.
- The bundled Lab interface connects and renders the graph.
- Data written before a restart is present afterwards with durability enabled.
Known sharp edges
- The entire graph must fit in memory; exceeding available RAM gets the process killed rather than spilling to disk.
- Durability depends on snapshot and write-ahead-log settings, and with defaults unchanged recent writes can be lost on an unclean shutdown.
- The platform image runs several processes in one container, so database, interface and console share a lifecycle and a log stream.
- Cypher compatibility with Neo4j is close but not complete; procedures and some clauses differ and queries should be tested rather than assumed portable.