The ArangoDB image bundles the database server binary, storage engine, query optimizer, cluster coordination agents, HTTP API and admin tools, a container entrypoint, and configuration templates. It exposes metrics and health endpoints and supports persistent volumes for data and TLS certificates for encrypted transport.
In containerized and production environments it runs as a single node or coordinated cluster under orchestration (Kubernetes, etc.), using liveness/readiness probes, persistent volume claims, and defined roles (coordinator/DB-Server/Agent). Operators deploy it with automated backups, monitoring, and configuration via mounted files or environment variables.
Typical workloads include transactional OLTP, analytical and ad‑hoc queries, graph traversals, and inverted‑index search. Teams evaluate an ArangoDB hardened image in secure or regulated environments to reduce attack surface, enforce non‑root execution, include fewer packages, provide signed artifacts, and apply stricter filesystem and crypto policies.
The Minimus ArangoDB image differs from typical ArangoDB container images by being built from scratch with only the essential components required to run the database, rather than layering a full general-purpose OS and toolchain. This design reduces the attack surface, yields a smaller, faster runtime footprint, and simplifies maintenance and patching, making it easier to reason about dependencies and runtime behavior for engineers and security teams.
The Minimus hardened ArangoDB image goes further by applying container and OS hardening practices aligned with industry standards such as NIST SP 800-190 and the CIS Benchmarks, including reduced runtime privileges, a stripped-down runtime environment, and a minimized update surface. These measures help streamline vulnerability management and operational hardening while preserving performance and maintainability for security-focused deployments.
ArangoDB is a multi-model database that combines document, graph, and key-value data models in a single engine, enabling flexible data modeling, rich graph traversals, and unified queries with AQL. It fits APIs, content management, recommendations, and real-time analytics. In containerized deployments, you typically deploy an ArangoDB image.
For production, use a hardened ArangoDB image and follow security best practices: authentication, TLS, backups, least privilege, and monitoring. Example:
docker run -d --name arango -e ARANGO_ROOT_PASSWORD=secret -p 8529:8529 arangodb:latestArangoDB is a multi-model database, while Neo4j is a native graph database focused on graphs. ArangoDB stores documents, key-value pairs, and graphs in a single engine, whereas Neo4j primarily stores nodes and relationships as a graph with optimized graph processing.
Querying differs: ArangoDB uses AQL (multi-model queries across document, key-value, and graph data), while Neo4j uses Cypher for graph patterns and traversals. This affects modelling choices and complexity of queries for complex connected data.
For deployment, ArangoDB supports sharding and distributed graphs; Neo4j offers causal clustering. If you deploy with containers, use an ArangoDB image; for production, consider a hardened ArangoDB image. The choice hinges on whether you need multi-model data or a purely graph-centric workload, as both provide enterprise features and answer different performance trade-offs.
Yes. ArangoDB Community Edition is free and open-source under Apache 2.0. The Enterprise Edition is paid and requires a license.
You can run ArangoDB for free using the official ArangoDB image from Docker Hub.
For production security, consider a hardened ArangoDB image or implement hardening practices in your container deployment.