DBMS > Amazon Redshift vs. CockroachDB vs. Drizzle vs. Geode vs. SAP SQL Anywhere

System Properties Comparison Amazon Redshift vs. CockroachDB vs. Drizzle vs. Geode vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

aws.amazon.com/redshift

www.cockroachlabs.com

geode.apache.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

geode.apache.org/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

Drizzle project, originally started by Brian Aker

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

SAP

formerly Sybase

Initial release

2012

2015

2008

2002

1992

Current release

24.1.0, May 2024

7.2.4, September 2012

1.1, February 2017

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

dynamic schema

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.

yes

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

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Java
PHP

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes, in C/C++, Java, .Net or Perl

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

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.