DBMS > Amazon DynamoDB vs. Citus vs. Riak TS vs. Tarantool vs. Transbase

System Properties Comparison Amazon DynamoDB vs. Citus vs. Riak TS vs. Tarantool vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

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

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

Spatial DBMS

with Tarantool/GIS 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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

aws.amazon.com/dynamodb

www.citusdata.com

www.tarantool.io

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

Technical documentation

docs.aws.amazon.com/dynamodb

docs.citusdata.com

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

www.tarantool.io/en/doc

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

Developer

Amazon

Open Source, formerly Basho Technologies

Transaction Software GmbH

Initial release

2012

2010

2015

2008

1987

Current release

8.1, December 2018

3.0.0, September 2022

2.10.0, May 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

AGPL, commercial license also available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

hosted

Linux

Linux
OS X

BSD
Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes, limited

Full-featured ANSI SQL support

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

Open binary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

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

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Erlang

Lua, C and SQL stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

pre-commit hooks and post-commit hooks

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Immediate Consistency

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets 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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.