DBMS > Amazon Redshift vs. Apache Kylin vs. CockroachDB vs. Hazelcast vs. STSdb

System Properties Comparison Amazon Redshift vs. Apache Kylin vs. CockroachDB vs. Hazelcast vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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 widely adopted in-memory data grid

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

aws.amazon.com/redshift

kylin.apache.org

www.cockroachlabs.com

hazelcast.com

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/redshift

kylin.apache.org/docs

www.cockroachlabs.com/docs

hazelcast.org/imdg/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation, originally contributed from eBay Inc

Cockroach Labs

Hazelcast

STS Soft SC

Initial release

2012

2015

2008

2011

Current release

3.1.0, July 2020

24.1.0, May 2024

5.3.6, November 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2, commercial license available

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

Linux
macOS
Windows

All OS with a Java VM

Windows

Data scheme

yes

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

the object must implement a serialization strategy

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for queries (using Apache Calcite)

yes, wire compatible with PostgreSQL

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C#
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

Triggers

yes

Events

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

yes

Replicated Map

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

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

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.