Neptune vs Titan

Neptune is a multiple database; Titan is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; Titan (2012, Apache-2.0, Java) is not ranked.

Attribute Neptune #4 ▼3 Leader Titan
At a glance
Rank #4— Not ranked
Score 65.5
GitHub stars 5.2k
Popularity 81.2
Activity 95.5
Community 53.7
Research 58.4
Fundamentals
Description 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).A distributed property graph database that stored graphs in pluggable backends such as Apache Cassandra, Apache HBase and Oracle BerkeleyDB, queried with Gremlin. Development stopped after DataStax acquired its developer Aurelius in 2015; continued as the JanusGraph fork and inside DataStax Enterprise Graph.
Vendor Amazon Web ServicesDataStax
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-112012
Status activedeprecated — No releases since 1.0 in September 2015. Development continued as JanusGraph.
License ProprietaryApache-2.0
Written in C++Java
Query languages Gremlin, SPARQL, openCypherGremlin
gdotv support yesno

Feature scores — not surveyed for Titan

Feature NeptuneTitan
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.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