DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. CockroachDB vs. etcd vs. XTDB

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. CockroachDB vs. etcd vs. XTDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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 distributed reliable key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Document store

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	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.cockroachlabs.com

etcd.io
github.com/etcd-io/etcd

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Cockroach Labs

Juxt Ltd.

Initial release

2012

2016

2015

2019

Current release

1703

24.1.0, May 2024

3.4, August 2019

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2.0

Open Source

MIT License

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

Server operating systems

hosted

Linux

Linux
macOS
Windows

FreeBSD
Linux
Windows

experimental

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

Schema and schema-less with LDAP views

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

LDAP

JDBC

gRPC
JSON over HTTP

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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 execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

LDAP bind authentication

Role-based access control

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.