ArangoDB vs Redland

ArangoDB is a multiple database; Redland is a rdf database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; Redland (2000, LGPL-2.1 OR GPL-2.0 OR Apache-2.0, C) ranks #68.

Attribute ArangoDB #2 = Leader Redland #68 ▲1 Growing
At a glance
Rank #2#68
Score 68.844.8
GitHub stars 14.3k105
Popularity 85.849.6
Activity 80.027.9
Community 51.656.3
Research 80.554.3
Fundamentals
Description 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.A modular C library suite for RDF storage, parsing, and querying. Comprises Raptor (parser/serializer), Rasqal (query engine), and librdf (storage API) with pluggable backends including Berkeley DB, PostgreSQL, MySQL, and SQLite. Provides bindings for Perl, Python, Ruby, and PHP.
Vendor ArangoDB IncDave Beckett
Model MultipleRDF
Kind databaselibrary
Category EnterpriseEstablished
First released 2012-032000
Status activeinactive — Mature project with periodic maintenance. Last release 2.0.18 in October 2024.
License BUSL-1.1LGPL-2.1 OR GPL-2.0 OR Apache-2.0
Written in C++C
Query languages AQLSPARQL
gdotv support nono

Feature scores — not surveyed for Redland

Feature ArangoDBRedland
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