DBMS > Amazon DynamoDB vs. RavenDB vs. TerminusDB vs. TigerGraph

System Properties Comparison Amazon DynamoDB vs. RavenDB vs. TerminusDB vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

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

Primary database model

Document store
Key-value store

Document store

Graph DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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.92
Rank	#101	Overall
	#18	Document stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/dynamodb

ravendb.net

terminusdb.com

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/dynamodb

ravendb.net/docs

terminusdb.github.io/terminusdb/#

docs.tigergraph.com

Developer

Amazon

Hibernating Rhinos

DataChemist Ltd.

Initial release

2012

2010

2018

2017

Current release

5.4, July 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

commercial

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

Prolog, Rust

C++

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

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 (RQL)

SQL-like query language (WOQL)

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript
Python

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Relationships in graphs

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, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

yes

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)

Authorization levels configured per client per database

Role-based access control

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.