DBMS > Amazon Redshift vs. atoti vs. Datomic vs. TerarkDB vs. VoltDB

System Properties Comparison Amazon Redshift vs. atoti vs. Datomic vs. TerarkDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

atoti.io

www.datomic.com

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.atoti.io

docs.datomic.com

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

ActiveViam

Cognitect

ByteDance, originally Terark

VoltDB Inc.

Initial release

2012

2016

2010

Current release

1.0.6735, June 2023

11.3, April 2022

License

Commercial or Open Source

commercial

free versions available

commercial

limited edition free

commercial

restricted open source version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, Clojure

C++

Java, C++

Server operating systems

hosted

All OS with a Java VM

Linux
OS X

for development

Data scheme

yes

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Multidimensional Expressions (MDX)

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Python

yes

Transaction Functions

Java

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

But extensive use of caching in the application peers

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Snapshots and command logging

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.