GDB-Engines

The go-to resource for graph technology details

About

Altair Graph Lakehouse vs ArangoDB

Altair Graph Lakehouse is a rdf database; ArangoDB is a multiple database. Altair Graph Lakehouse (2018-10, Proprietary, C++) ranks #89 this month; ArangoDB (2012-03, BSL-1.1, C++) ranks #2. They differ on 17 of 46 surveyed features.

Attribute Altair Graph Lakehouse #89 ▲13 Growing ArangoDB #2 = Leader
At a glance
Rank #89#2
Score 38.867.5
GitHub stars 14.2k
Popularity 59.487.7
Activity 74.0
Community 31.052.0
Research 50.478.9
Fundamentals
Description An RDF graph OLAP database (formerly AnzoGraph DB) using massively parallel processing (MPP) for analytical workloads. Rebranded under Altair, it supports SPARQL 1.1 with extensions for window aggregates and advanced grouping, plus openCypher query support.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.
Vendor AltairArangoDB Inc
Model RDFMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2018-102012-03
Status activeactive
License ProprietaryBSL-1.1
Written in C++C++
Query languages SPARQL, openCypherAQL
gdotv support nono

Feature scores 17 of 46 rows differ

Feature Altair Graph LakehouseArangoDB
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 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