DBMS > Amazon DynamoDB vs. Riak KV vs. TerminusDB vs. Transbase

System Properties Comparison Amazon DynamoDB vs. Riak KV vs. TerminusDB vs. Transbase

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

Distributed, fault tolerant key-value store

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Graph DBMS

Relational DBMS

Secondary database models

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	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

aws.amazon.com/dynamodb

terminusdb.com

www.transaction.de/en/products/transbase.html

Technical documentation

docs.aws.amazon.com/dynamodb

www.tiot.jp/riak-docs/riak/kv/latest

terminusdb.github.io/terminusdb/#

www.transaction.de/en/products/transbase/features.html

Developer

Amazon

OpenSource, formerly Basho Technologies

DataChemist Ltd.

Transaction Software GmbH

Initial release

2012

2009

2018

1987

Current release

3.2.0, December 2022

11.0.0, January 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

commercial

free development license

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

Prolog, Rust

C and C++

Server operating systems

hosted

Linux
OS X

Linux

FreeBSD
Linux
macOS
Solaris
Windows

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

restricted

yes

SQL

Support of SQL

SQL-like query language (WOQL)

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

yes

Triggers

yes

by integration with AWS Lambda

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Journaling Streams

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

Foreign keys

Referential integrity

links between data sets can be stored

yes

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

yes

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)

yes, using Riak Security

Role-based access control

fine grained access rights according to SQL-standard

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.