DBMS > Amazon DynamoDB vs. CockroachDB vs. Newts vs. Tarantool vs. Teradata

System Properties Comparison Amazon DynamoDB vs. CockroachDB vs. Newts vs. Tarantool vs. Teradata

Editorial information provided by DB-Engines

Name

Description

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Time Series DBMS based on Cassandra

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

A hybrid cloud data analytics software platform (Teradata Vantage)

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

Spatial DBMS

with Tarantool/GIS extension

Document store
Graph DBMS
Spatial DBMS
Time Series 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	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

aws.amazon.com/dynamodb

www.cockroachlabs.com

opennms.github.io/newts

www.tarantool.io

www.teradata.com

Technical documentation

docs.aws.amazon.com/dynamodb

www.cockroachlabs.com/docs

github.com/OpenNMS/newts/wiki

www.tarantool.io/en/doc

docs.teradata.com

Developer

Amazon

Cockroach Labs

OpenNMS Group

Teradata

Initial release

2012

2015

2014

2008

1984

Current release

23.1.1, May 2023

2.10.0, May 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0, commercial license available

Open Source

Apache 2.0

Open Source

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

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

Java

C and C++

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X
Windows

BSD
Linux
macOS

hosted
Linux

Data scheme

schema-free

dynamic schema

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

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes, wire compatible with PostgreSQL

Full-featured ANSI SQL support

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP API

JDBC

HTTP REST
Java API

Open binary protocol

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Java

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

by integration with AWS Lambda

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

based on Cassandra

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

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

selectable replication factor

based on Cassandra

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

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)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

ACID

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

yes

User concepts

Access control

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

Role-based access control

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.