ArangoDB vs FlockDB

ArangoDB is a multiple database; FlockDB is a other database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; FlockDB (2010-04, Apache-2.0, Scala) ranks #67.

Attribute ArangoDB #2 = Leader FlockDB #67 ▲5 Growing
At a glance
Rank #2#67
Score 68.845.1
GitHub stars 14.3k3.3k
Popularity 85.852.1
Activity 80.028.8
Community 51.648.3
Research 80.549.6
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 distributed graph database built by Twitter for storing adjacency lists, optimized for wide and shallow social graphs like follower relationships. Supports set arithmetic queries but intentionally avoids multi-hop graph traversal.
Vendor ArangoDB IncTwitter (now X)
Model MultipleOther
Kind databasedatabase
Category EnterpriseEstablished
First released 2012-032010-04
Status activeinactive — Archived and unmaintained since 2017. Twitter is no longer responding to issues or PRs.
License BUSL-1.1Apache-2.0
Written in C++Scala
Query languages AQLThrift API
gdotv support nono

Feature scores — not surveyed for FlockDB

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