DBMS > Amazon Redshift vs. Datomic vs. IBM Db2 warehouse vs. NSDb vs. PlanetScale

System Properties Comparison Amazon Redshift vs. Datomic vs. IBM Db2 warehouse vs. NSDb vs. PlanetScale

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Cloud-based data warehousing service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/redshift

www.datomic.com

www.ibm.com/products/db2/warehouse

nsdb.io

planetscale.com

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

nsdb.io/Architecture

planetscale.com/docs

Developer

Amazon (based on PostgreSQL)

Cognitect

IBM

PlanetScale

Initial release

2012

2014

2017

2020

Current release

1.0.6735, June 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache Version 2.0

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, Clojure

Java, Scala

Server operating systems

hosted

All OS with a Java VM

hosted

Linux
macOS

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

Import/export of XML data possible

Secondary indexes

restricted

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

.NET Client API
JDBC
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Java
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

PL/SQL, SQL PL

yes

proprietary syntax

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

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

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

yes

Using Apache Lucene

yes

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 with fine-grained authorization concept

no user groups or 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.