DBMS > Amazon Neptune vs. Apache Druid vs. MySQL vs. Titan

System Properties Comparison Amazon Neptune vs. Apache Druid vs. MySQL vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Fast, reliable graph database built for the cloud

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Widely used open source RDBMS

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Graph DBMS
RDF store

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/neptune

druid.apache.org

www.mysql.com

github.com/thinkaurelius/titan

Technical documentation

aws.amazon.com/neptune/developer-resources

druid.apache.org/docs/latest/design

dev.mysql.com/doc

github.com/thinkaurelius/titan/wiki

Developer

Amazon

Apache Software Foundation and contributors

Oracle

since 2010, originally MySQL AB, then Sun

Aurelius, owned by DataStax

Initial release

2017

2012

1995

2012

Current release

30.0.0, June 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache license, version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Java

Server operating systems

hosted

Linux
OS X
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

schema-less columns are supported

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

with proprietary extensions

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

yes

Relationships in graph

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Users with fine-grained authorization concept

no user groups or roles

User authentification and security via Rexster Graph Server

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.