Cray Graph Engine vs FalkorDB

Cray Graph Engine is a other database; FalkorDB is a property graph database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #78 this month; FalkorDB (2018-07, SSPL-1.0, C) ranks #6. They differ on 23 of 46 surveyed features.

Attribute Cray Graph Engine #78 ▲2 Growing FalkorDB #6 ▼2 Strong
At a glance
Rank #78#6
Score 42.364.6
GitHub stars 6.2k
Popularity 77.263.1
Activity 80.0
Community 30.672.1
Research 51.054.3
Fundamentals
Description An RDF triple store built for Cray/HPE supercomputer systems. Uses a shared global address space across compute nodes for distributed graph analytics with pre-built graph algorithms.A property graph database that runs as a Redis module, formerly RedisGraph. Uses GraphBLAS sparse matrix operations for query execution, enabling parallel graph traversal.
Vendor Hewlett Packard EnterpriseFalkorDB
Model OtherProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2015-032018-07
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietarySSPL-1.0
Written in C++C
Query languages SPARQLopenCypher
gdotv support noyes

Feature scores 23 of 46 rows differ

Feature Cray Graph EngineFalkorDB
Community & Business
Active development
Commercial support
Live community ·
Open Source ·
Pricing ·
Trendiness ·0.5
Deployment
Containerization ·
Work as dedicated instance
Work as embedded ··
Testing in-memory version ·
Platform
Operating on Linux
Operating on Windows ·0.75
SaaS offering ··
Operations
Automatic updates ··
Client side caching ·0.5
Data versioning support ··
Live backups 0.5
Distribution
Cluster Re-balancing ··
Data Distribution ·
High-Availability 0.50.5
Query Distribution ·
Replication support ·
Developer Experience
Data types defined 0.5
Logging/Auditing 0.5
Object-Graph Mapper
Reactive programming ·0.5
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 0.5
Schema support 0.5·
Secondary indexes
Server side procedures
Triggers ·0.5
Authentication 0.5
Authorization 0.5
Data encryption ·0.5