GDB-Engines

The go-to resource for graph technology details

About

Altair Graph Lakehouse vs Neptune

Altair Graph Lakehouse is a rdf database; Neptune is a multiple database. Altair Graph Lakehouse (2018-10, Proprietary, C++) ranks #89 this month; Neptune (2017-11, Proprietary) ranks #7. They differ on 16 of 46 surveyed features.

Attribute Altair Graph Lakehouse #89 ▲13 Growing Neptune #7 = Strong
At a glance
Rank #89#7
Score 38.863.3
GitHub stars
Popularity 59.467.3
Activity 99.0
Community 31.053.9
Research 50.459.1
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 fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries).
Vendor AltairAmazon Web Services
Model RDFMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2018-102017-11
Status activeactive
License ProprietaryProprietary
Written in C++
Query languages SPARQL, openCypherGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 16 of 46 rows differ

Feature Altair Graph LakehouseNeptune
Community & Business
Active development
Commercial support
Live community ·
Open Source ··
Pricing
Trendiness
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 0.5
Replication support
Developer Experience
Data types defined 0.50.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
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction ·
Transaction support
Schema & Security
Constraints ·
Schema support 0.5
Secondary indexes
Server side procedures ··
Triggers ··
Authentication
Authorization
Data encryption