ArangoDB
futomaki.arangodb
Multi-model database holding documents, graphs and key-value pairs in one engine, queried through a single declarative language, AQL, that joins and traverses across all three in one statement.
A Docker Compose file for ArangoDB alone, generated from the catalog and checked by the safety inspector. Sign in and use Kitchen Credits to activate it.
Uses the Medusa cart and payment-session path. This test control does not create an order or capture payment.
ArangoDB stores every record as a JSON document in a collection, and edge collections give those documents typed relationships, which turns the same data into a traversable graph without introducing a second system. AQL expresses filters, joins, graph traversals and aggregations together, and search and vector indexes are built over the same collections rather than a copy of them. Deployments run as a single server or as a cluster of coordinators and database servers holding sharded collections. A first deployment creates a database, loads a document collection and an edge collection, and runs a traversal across them.
You know it worked when
- The web interface loads and authenticates against the configured credentials.
- A database and document collection can be created and a document inserted.
- An AQL query returns that document.
- A traversal across an edge collection returns the expected connected documents.
Known sharp edges
- The container refuses to start unless a root password or an explicit no-authentication flag is supplied through the environment.
- A moving tag can cross a major version between pulls, and an ArangoDB upgrade applies irreversible changes to the data directory.
- The 100 GiB Community Licence ceiling is a legal limit, not a technical one, and nothing in the software warns when a deployment crosses it.
- Graph traversals degrade to full scans without an index on the edge collection, which only becomes visible as the graph grows.