ArangoDB vs Teradata Aster

ArangoDB is a multiple database; Teradata Aster is a property graph database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; Teradata Aster (2013-10, Proprietary) is not ranked.

Attribute ArangoDB #2 = Leader Teradata Aster
At a glance
Rank #2— Not ranked
Score 68.8
GitHub stars 14.3k
Popularity 85.8
Activity 80.0
Community 51.6
Research 80.5
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 massively parallel analytics database whose SQL-GR engine, added in Aster 6, runs vertex-oriented graph algorithms in bulk-synchronous parallel steps and invokes them from SQL alongside SQL-MapReduce functions. Its engines were folded into Teradata Vantage in 2018.
Vendor ArangoDB IncTeradata
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEnterprise
First released 2012-032013-10
Status activedeprecated — Last standalone release was Aster 7 in 2016; its engines were folded into Teradata Vantage in 2018.
License BUSL-1.1Proprietary
Written in C++
Query languages AQLSQL
gdotv support nono

Feature scores — not surveyed for Teradata Aster

Feature ArangoDBTeradata Aster
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