GDB-Engines

The go-to resource for graph technology details

About

ArangoDB vs TigerGraph

ArangoDB is a multiple database; TigerGraph is a property graph database. ArangoDB (2012-03, BSL-1.1, C++) ranks #2 this month; TigerGraph (2017, Proprietary, C++) ranks #23. They differ on 19 of 46 surveyed features.

Attribute ArangoDB #2 = Leader TigerGraph #23 ▲7 Strong
At a glance
Rank #2#23
Score 67.557.1
GitHub stars 14.2k
Popularity 87.740.3
Activity 74.089.6
Community 52.057.4
Research 78.960.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 property graph database (formerly GraphSQL) built for massively parallel processing and graph analytics. Uses the SQL-like GSQL query language and supports ACID transactions. Available in developer, cloud, and enterprise editions.
Vendor ArangoDB IncTigerGraph
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2012-032017
Status activeactive
License BSL-1.1Proprietary
Written in C++C++
Query languages AQLGSQL
gdotv support nono

Feature scores 19 of 46 rows differ

Feature ArangoDBTigerGraph
Community & Business
Active development
Commercial support
Live community 0.50.5
Open Source ·
Pricing ··
Trendiness 0.250.5
Deployment
Containerization
Work as dedicated instance
Work as embedded ·
Testing in-memory version 0.5
Platform
Operating on Linux
Operating on Windows 0.5
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 0.5
Developer Experience
Data types defined
Logging/Auditing 0.5
Object-Graph Mapper ·
Reactive programming ··
Documentation up-to-date 0.75
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 ·0.5
Transaction support
Schema & Security
Constraints ·
Schema support 0.5
Secondary indexes ·
Server side procedures 0.5
Triggers ··
Authentication
Authorization 0.5
Data encryption