GDB-Engines

The go-to resource for graph technology details

About

JanusGraph vs Neptune

JanusGraph is a property graph database; Neptune is a multiple database. JanusGraph (2017-04, Apache-2.0, Java) ranks #35 this month; Neptune (2017-11, Proprietary) ranks #7. They differ on 22 of 46 surveyed features.

Attribute JanusGraph #35 ▲5 Strong Neptune #7 = Strong
At a glance
Rank #35#7
Score 53.263.3
GitHub stars 5.8k
Popularity 79.367.3
Activity 40.999.0
Community 37.153.9
Research 63.459.1
Fundamentals
Description An open-source distributed property graph database forked from the Titan codebase. Supports pluggable storage backends (Cassandra, HBase, BerkeleyDB) with ACID transactions and native TinkerPop integration.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 The Linux FoundationAmazon Web Services
Model Property GraphMultiple
Kind databasedatabase
Category EstablishedEnterprise
First released 2017-042017-11
Status activeactive
License Apache-2.0Proprietary
Written in Java
Query languages GremlinGremlin, SPARQL, openCypher
gdotv support yesyes

Feature scores 22 of 46 rows differ

Feature JanusGraphNeptune
Community & Business
Active development
Commercial support ·
Live community
Open Source ·
Pricing
Trendiness 0.5
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.75
Binary protocol
CLI
GUI ·
Data Model
Multi-database ·
Graph-native data
REST API
Query Language
Transactions
Granular locking 0.5
Multiple isolation levels 0.5
Read committed transaction 0.5
Transaction support
Schema & Security
Constraints
Schema support 0.5
Secondary indexes
Server side procedures ··
Triggers 0.5·
Authentication
Authorization
Data encryption ·