ByteGraph vs Neptune

ByteGraph is a other database; Neptune is a multiple database. ByteGraph (2018, Proprietary, C++) ranks #69 this month; Neptune (2017-11, Proprietary, C++) ranks #4. They differ on 26 of 46 surveyed features.

Attribute ByteGraph #69 ▼12 Growing Neptune #4 ▼3 Leader
At a glance
Rank #69#4
Score 43.565.5
GitHub stars
Popularity 68.281.2
Activity 95.5
Community 30.653.7
Research 53.958.4
Fundamentals
Description An internal ByteDance distributed graph database using a two-tier architecture with durable storage and cache layers. Optimizes for social graph workloads with an edge-tree data structure and adaptive caching. Not publicly available.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 ByteDanceAmazon Web Services
Model OtherMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 20182017-11
Status inactive — ByteDance internal system. Not publicly available.active
License ProprietaryProprietary
Written in C++C++
Query languages GremlinGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 26 of 46 rows differ

Feature ByteGraphNeptune
Community & Business
Active development ·
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.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 ·