DBMS > Amazon Redshift vs. Datomic vs. Microsoft Azure Synapse Analytics vs. PlanetScale vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Datomic vs. Microsoft Azure Synapse Analytics vs. PlanetScale vs. TerarkDB

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

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

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

aws.amazon.com/redshift

www.datomic.com

azure.microsoft.com/services/synapse-analytics

planetscale.com

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

docs.microsoft.com/azure/synapse-analytics

planetscale.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Cognitect

Microsoft

PlanetScale

ByteDance, originally Terark

Initial release

2012

2016

2020

2016

Current release

1.0.6735, June 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

restricted open source version available

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

C++

Server operating systems

hosted

All OS with a Java VM

hosted

Docker
Linux
macOS

Data scheme

yes

schema-free

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

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C#
Java
PHP

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Transact SQL

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, horizontal partitioning

Sharding

none

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

yes

Durability

Support for making data persistent

yes

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

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

yes

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.