DBMS > Amazon DynamoDB vs. Amazon Neptune vs. JanusGraph vs. TigerGraph vs. VoltDB

System Properties Comparison Amazon DynamoDB vs. Amazon Neptune vs. JanusGraph vs. TigerGraph vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Fast, reliable graph database built for the cloud

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Graph DBMS

Relational DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

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

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/dynamodb

aws.amazon.com/neptune

janusgraph.org

www.tigergraph.com

www.voltdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

aws.amazon.com/neptune/developer-resources

docs.janusgraph.org

docs.tigergraph.com

docs.voltdb.com

Developer

Amazon

Linux Foundation; originally developed as Titan by Aurelius

VoltDB Inc.

Initial release

2012

2017

2010

Current release

0.6.3, February 2023

11.3, April 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

Java, C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux

Linux
OS X

for development

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GSQL)

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Clojure
Java
Python

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

yes

Relationships in graphs

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

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

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

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

User authentification and security via Rexster Graph Server

Role-based access control

Users and roles with access to stored procedures

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.