BlazeGraph vs Neptune

BlazeGraph is a rdf database; Neptune is a multiple database. BlazeGraph (2007, GPL-2.0, Java) ranks #73 this month; Neptune (2017-11, Proprietary, C++) ranks #4. They differ on 22 of 46 surveyed features.

Attribute BlazeGraph #73 ▼2 Growing Neptune #4 ▼3 Leader
At a glance
Rank #73#4
Score 43.165.5
GitHub stars 989
Popularity 58.581.2
Activity 25.295.5
Community 35.353.7
Research 49.658.4
Fundamentals
Description An RDF database supporting billions of edges on a single machine. Uses an alternative approach to RDF reification that enables property graph-like capabilities. Notable as the backend for Wikidata's query service.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 SYSTAPAmazon Web Services
Model RDFMultiple
Kind databasedatabase
Category EstablishedEnterprise
First released 20072017-11
Status inactive — Last release in 2019. Project largely dormant, though still used by Wikidata.active
License GPL-2.0Proprietary
Written in JavaC++
Query languages SPARQL, GremlinGremlin, SPARQL, openCypher
gdotv support yesyes

Feature scores 22 of 46 rows differ

Feature BlazeGraphNeptune
Community & Business
Active development ·
Commercial support ·
Live community 0.25
Open Source ·
Pricing ·
Trendiness
Deployment
Containerization ··
Work as dedicated instance
Work as embedded ·
Testing in-memory version ··
Platform
Operating on Linux 0.75
Operating on Windows 0.75·
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 ·