DBMS > Amazon Redshift vs. CrateDB vs. Heroic vs. KairosDB

System Properties Comparison Amazon Redshift vs. CrateDB vs. Heroic vs. KairosDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed Database based on Lucene

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Time Series 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.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Website

aws.amazon.com/redshift

cratedb.com

github.com/spotify/heroic

github.com/kairosdb/kairosdb

Technical documentation

docs.aws.amazon.com/redshift

cratedb.com/docs

spotify.github.io/heroic

kairosdb.github.io

Developer

Amazon (based on PostgreSQL)

Crate

Spotify

Initial release

2012

2013

2014

2013

Current release

5.8.1, August 2024

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

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

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X
Windows

Data scheme

yes

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

schema-free

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.

Secondary indexes

restricted

yes

via Elasticsearch

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

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

.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

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions (Javascript)

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

yes

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency
Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

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

rights management via user accounts

simple password-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.