G-Tran vs Neo4j

G-Tran is a other database; Neo4j is a property graph database. G-Tran (2019-03, Apache-2.0, C++) ranks #126 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 28 of 46 surveyed features.

Attribute G-Tran #126 ▲3 Emerging Neo4j #1 = Leader
At a glance
Rank #126#1
Score 24.283.3
GitHub stars 1817.2k
Popularity 29.897.3
Activity 39.186.7
Community 43.190.2
Research 50.798.6
Fundamentals
Description A research prototype for graph transaction processing. Supports ACID transactions on property graphs with a focus on concurrent workload optimization.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 Neo4j Inc
Model OtherProperty Graph
Kind databasedatabase
Category EmergingEstablished
First released 2019-032007
Status inactive — Academic research prototype. No active development.active
License Apache-2.0GPL-3.0
Written in C++Java
Query languages GremlinCypher, GQL
gdotv support noyes

Feature scores 28 of 46 rows differ

Feature G-TranNeo4j
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 ··