GDB-Engines

The go-to resource for graph technology details

About

agdb vs ArangoDB

agdb is a property graph database; ArangoDB is a multiple database. agdb (2023-06, Apache-2.0, Rust) ranks #112 this month; ArangoDB (2012-03, BSL-1.1, C++) ranks #2.

Attribute agdb #112 ▲7 Emerging ArangoDB #2 = Leader
At a glance
Rank #112#2
Score 29.667.5
GitHub stars 13714.2k
Popularity 29.587.7
Activity 69.874.0
Community 31.052.0
Research 60.178.9
Fundamentals
Description An application-native graph database written in Rust using programmatic query builders instead of a text-based query language. Features ACID transactions, memory-mapped persistent storage, and client libraries for Rust, Python, TypeScript, PHP, Java, C, C++, and C#.A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model. Offers both an in-memory storage engine and a RocksDB-based engine for larger datasets.
Vendor AgnesoftArangoDB Inc
Model Property GraphMultiple
Kind embeddeddatabase
Category EmergingEnterprise
First released 2023-062012-03
Status activeactive
License Apache-2.0BSL-1.1
Written in RustC++
Query languages Custom APIAQL
gdotv support nono

Feature scores — not surveyed for agdb

Feature agdbArangoDB
Community & Business
Active development
Commercial support
Live community 0.5
Open Source
Pricing ·
Trendiness 0.25
Deployment
Containerization
Work as dedicated instance
Work as embedded ·
Testing in-memory version
Platform
Operating on Linux
Operating on Windows
SaaS offering ·
Operations
Automatic updates ·
Client side caching ·
Data versioning support ·
Live backups
Distribution
Cluster Re-balancing
Data Distribution
High-Availability
Query Distribution
Replication support
Developer Experience
Data types defined
Logging/Auditing
Object-Graph Mapper
Reactive programming ·
Documentation up-to-date
Binary protocol
CLI
GUI
Data Model
Multi-database
Graph-native data ·
REST API
Query Language 0.5
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction ·
Transaction support
Schema & Security
Constraints
Schema support 0.5
Secondary indexes
Server side procedures 0.5
Triggers ·
Authentication
Authorization 0.5
Data encryption