ChronoGraph vs OrientDB

ChronoGraph is a property graph database; OrientDB is a multiple database. ChronoGraph (2017-02, AGPL-3.0, Java) ranks #145 this month; OrientDB (2010, Apache-2.0, Java) ranks #11. They differ on 26 of 46 surveyed features.

Attribute ChronoGraph #145 ▲5 Emerging OrientDB #11 ▲6 Strong
At a glance
Rank #145#11
Score 14.062.9
GitHub stars 545k
Popularity 34.380.4
Activity 27.962.5
Community 41.157.4
Research 64.8
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 distributed multi-model database combining graph and document models with TinkerPop support. Features sharding for horizontal scaling and ACID transactions.
Vendor OrientDB Community
Model Property GraphMultiple
Kind embeddeddatabase
Category EmergingEnterprise
First released 2017-022010
Status inactive — Last meaningful commit several years ago. Minimal community.active
License AGPL-3.0Apache-2.0
Written in JavaJava
Query languages GremlinSQL, Gremlin
gdotv support nono

Feature scores 26 of 46 rows differ

Feature ChronoGraphOrientDB
Community & Business
Active development 0.25
Commercial support ·
Live community ·0.5
Open Source
Pricing ··
Trendiness ·0.25
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
Logging/Auditing
Object-Graph Mapper ·
Reactive programming ··
Documentation up-to-date 0.250.5
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.5
Secondary indexes
Server side procedures ·
Triggers ·
Authentication ·
Authorization ·
Data encryption ·