DBMS > Amazon Redshift vs. CockroachDB vs. EsgynDB vs. H2GIS vs. PlanetScale

System Properties Comparison Amazon Redshift vs. CockroachDB vs. EsgynDB vs. H2GIS vs. PlanetScale

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial extension of H2

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

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/redshift

www.cockroachlabs.com

www.esgyn.cn

www.h2gis.org

planetscale.com

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

www.h2gis.org/docs/home

planetscale.com/docs

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

Esgyn

CNRS

PlanetScale

Initial release

2012

2015

2013

2020

Current release

23.1.1, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

Open Source

LGPL 3.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

C++, Java

Java

Server operating systems

hosted

Linux
macOS
Windows

Linux

Docker
Linux
macOS

Data scheme

yes

dynamic schema

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

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/ADO.Net

Java

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

Java Stored Procedures

yes

based on H2

yes

proprietary syntax

Triggers

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

Multi-source replication between multi datacenters

yes

based on H2

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

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

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

fine grained access rights according to SQL-standard

yes

based on H2

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.