DBMS > Amazon Redshift vs. CockroachDB vs. FatDB vs. Geode vs. OpenTSDB

System Properties Comparison Amazon Redshift vs. CockroachDB vs. FatDB vs. Geode vs. OpenTSDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Scalable Time Series DBMS based on HBase

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Time Series 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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Website

aws.amazon.com/redshift

www.cockroachlabs.com

geode.apache.org

opentsdb.net

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

geode.apache.org/docs

opentsdb.net/docs/build/html/index.html

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

FatCloud

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

currently maintained by Yahoo and other contributors

Initial release

2012

2015

2012

2002

2011

Current release

23.1.1, May 2023

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

LGPL

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

Server operating systems

hosted

Linux
macOS
Windows

Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

Data scheme

yes

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

Via inetgration in SQL Server

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

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

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

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Cache Event Listeners

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

selectable replication factor

Multi-source replication

selectable replication factor

based on HBase

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
Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

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

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

Can implement custom security layer via applications

Access rights per client and object definable

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.