DBMS > Amazon DynamoDB vs. CouchDB vs. MaxDB vs. TigerGraph vs. ToroDB

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. MaxDB vs. TigerGraph vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A robust and reliable RDBMS optimized to run all major SAP solutions

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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	9.30
Rank	#45	Overall
	#7	Document stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/dynamodb

couchdb.apache.org

maxdb.sap.com

www.tigergraph.com

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

maxdb.sap.com/documentation

docs.tigergraph.com

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

SAP, acquired from Software AG (Adabas-D) in 1997

8Kdata

Initial release

2012

2005

1984

2017

2016

Current release

3.3.3, December 2023

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

commercial

Limited community edition free

commercial

Open Source

AGPL-V3

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

Erlang

C++

Java

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

via views

yes

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
WebDAV

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C#
Java
Perl
PHP
Python

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

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

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

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)

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Role-based access control

Access rights for users and roles

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.