ChronoGraph vs Neptune

ChronoGraph is a property graph database; Neptune is a multiple database. ChronoGraph (2017-02, AGPL-3.0, Java) ranks #145 this month; Neptune (2017-11, Proprietary, C++) ranks #4. They differ on 29 of 46 surveyed features.

Attribute ChronoGraph #145 ▲5 Emerging Neptune #4 ▼3 Leader
At a glance
Rank #145#4
Score 14.065.5
GitHub stars 54
Popularity 34.381.2
Activity 27.995.5
Community 41.153.7
Research 58.4
Fundamentals
Description A TinkerPop-compliant embedded graph database with system-time content versioning. Implemented as a temporally-enhanced key-value store using B-tree structures, enabling historical graph queries and analysis.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 Amazon Web Services
Model Property GraphMultiple
Kind embeddeddatabase
Category EmergingEnterprise
First released 2017-022017-11
Status inactive — Last meaningful commit several years ago. Minimal community.active
License AGPL-3.0Proprietary
Written in JavaC++
Query languages GremlinGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 29 of 46 rows differ

Feature ChronoGraphNeptune
Community & Business
Active development 0.25
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.5
Logging/Auditing
Object-Graph Mapper ·
Reactive programming ·
Documentation up-to-date 0.25
Binary protocol 0.75
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.50.5
Secondary indexes
Server side procedures ··
Triggers ··
Authentication ·
Authorization ·
Data encryption ·