GDB-Engines

The go-to resource for graph technology details

About

ArangoDB vs SAP Hana

Both are multiple databases. ArangoDB (2012-03, BSL-1.1, C++) ranks #2 this month; SAP Hana (2010, Proprietary, C++) ranks #24. They differ on 19 of 46 surveyed features.

Attribute ArangoDB #2 = Leader SAP Hana #24 ▲1 Strong
At a glance
Rank #2#24
Score 67.556.7
GitHub stars 14.2k
Popularity 87.774.2
Activity 74.049.8
Community 52.043.4
Research 78.997.3
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 multi-model in-memory database with built-in graph engine supporting both property graphs and knowledge graphs. Provides built-in graph algorithms for path finding and network analysis. Part of SAP Business Technology Platform.
Vendor ArangoDB IncSAP
Model MultipleMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2012-032010
Status activeactive
License BSL-1.1Proprietary
Written in C++C++
Query languages AQLSQL, openCypher, GraphScript
gdotv support nono

Feature scores 19 of 46 rows differ

Feature ArangoDBSAP Hana
Community & Business
Active development 0.5
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