DBMS > Amazon Redshift vs. CockroachDB vs. Datomic vs. Firebird vs. RethinkDB

System Properties Comparison Amazon Redshift vs. CockroachDB vs. Datomic vs. Firebird vs. RethinkDB

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.

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

Firebird is an open source RDBMS forked from Borland's InterBase

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	2.84
Rank	#106	Overall
	#19	Document stores

Website

aws.amazon.com/redshift

www.cockroachlabs.com

www.datomic.com

www.firebirdsql.org

rethinkdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

docs.datomic.com

www.firebirdsql.org/en/reference-manuals

rethinkdb.com/docs

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

Cognitect

Firebird Foundation

The Linux Foundation

since July 2017

Initial release

2012

2015

2012

2000

As fork of Borland's InterBase

2009

Current release

23.1.1, May 2023

1.0.6735, June 2023

5.0.0, January 2024

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Open Source

Initial Developer's Public License

Open Source

Apache Version 2

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 and C++

C++

Server operating systems

hosted

Linux
macOS
Windows

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

APIs and other access methods

JDBC
ODBC

JDBC

RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

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

Clojure
Java

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

PSQL

Triggers

By using transaction functions

yes

Client-side triggers through changefeeds

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

none

But extensive use of caching in the application peers

none

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

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

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

MVCC based

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

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

Users with fine-grained authorization concept

yes

users and table-level permissions

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.