DBMS > Amazon Redshift vs. Axibase vs. Hazelcast vs. RethinkDB

System Properties Comparison Amazon Redshift vs. Axibase vs. Hazelcast vs. RethinkDB

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

A widely adopted in-memory data grid

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

hazelcast.com

rethinkdb.com

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

rethinkdb.com/docs

Developer

Amazon (based on PostgreSQL)

Axibase Corporation

Hazelcast

The Linux Foundation

since July 2017

Initial release

2012

2013

2008

2009

Current release

15585

5.3.6, November 2023

2.4.1, August 2020

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache Version 2; commercial licenses available

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

C++

Server operating systems

hosted

Linux

All OS with a Java VM

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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.

yes

the object must implement a serialization strategy

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

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

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

Event Listeners, Executor Services

Triggers

yes

Events

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Replicated Map

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

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

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

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.