Altair Graph Lakehouse vs Neo4j
Altair Graph Lakehouse is a rdf database; Neo4j is a property graph database. Altair Graph Lakehouse (2018-10, Proprietary, C++) ranks #89 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 19 of 46 surveyed features.
| Attribute |  Altair Graph Lakehouse |  Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #89 | #1 |
| Score | 38.8 | 78.8 |
| GitHub stars | — | 17k |
| Popularity | 59.4 | 93.8 |
| Activity | — | 82.8 |
| Community | 31.0 | 77.2 |
| Research | 50.4 | 98.6 |
| 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 property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library. |
| Vendor | Altair | Neo4j Inc |
| Model | RDF | Property Graph |
| Kind | database | database |
| Category | Enterprise | Established |
| First released | 2018-10 | 2007 |
| Status | active | active |
| License | Proprietary | GPL-3.0 |
| Written in | C++ | Java |
| Query languages | SPARQL, openCypher | Cypher, GQL |
| gdotv support | no | yes |
Feature scores 19 of 46 rows differ
| Feature | Altair Graph Lakehouse | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | · | ✓ |
| Open Source | · | ✓ |
| Pricing | ✓ | 0.5 |
| 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 | ✓ | ✓ |
| 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 | ✓ | ✓ |
| Transactions | ||
| Granular locking | · | ✓ |
| Multiple isolation levels | · | ✓ |
| Read committed transaction | · | ✓ |
| Transaction support | ✓ | ✓ |
| Schema & Security | ||
| Constraints | · | ✓ |
| Schema support | ✓ | ✓ |
| Secondary indexes | ✓ | ✓ |
| Server side procedures | · | ✓ |
| Triggers | · | ✓ |
| Authentication | ✓ | ✓ |
| Authorization | ✓ | ✓ |
| Data encryption | ✓ | · |
Links
- Altair Graph Lakehouse · website · full profile
- Neo4j · website · github · full profile