ArangoDB vs ZipG

ArangoDB is a multiple database; ZipG is a other database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; ZipG (2017, C++) ranks #80. They differ on 28 of 46 surveyed features.

Attribute ArangoDB #2 = Leader ZipG #80 ▼3 Growing
At a glance
Rank #2#80
Score 68.842.3
GitHub stars 14.3k13
Popularity 85.829.6
Activity 80.029.7
Community 51.664.7
Research 80.552.1
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 research prototype graph store that executes queries directly on a compressed graph representation for memory efficiency. Lacks traditional database features such as transactions and replication.
Vendor ArangoDB Inc
Model MultipleOther
Kind databaseembedded
Category EnterpriseEmerging
First released 2012-032017
Status activeinactive — Academic research prototype from AMPLab Berkeley. No active development.
License BUSL-1.1
Written in C++C++
Query languages AQLCustom API
gdotv support nono

Feature scores 28 of 46 rows differ

Feature ArangoDBZipG
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 0.75
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 0.5
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 ·