DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. BigchainDB vs. CrateDB

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. BigchainDB vs. CrateDB

Please select another system to include it in the comparison.

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Distributed Database based on Lucene

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Secondary database models

Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Website

aws.amazon.com/redshift

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

www.bigchaindb.com

cratedb.com

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

cratedb.com/docs

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Crate

Initial release

2012

2016

2013

Current release

1703

5.8.1, August 2024

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

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

Python

Java

Server operating systems

hosted

Linux

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

optional

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, but no triggers and constraints, and PostgreSQL compatibility

APIs and other access methods

JDBC
ODBC

LDAP

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions (Javascript)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Configurable replication on table/partition-level

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

Eventual Consistency
Read-after-write consistency on record level

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic execution of specific operations

unique row identifiers can be used for implementing an optimistic concurrency control strategy

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

LDAP bind authentication

yes

rights management via user accounts

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.