DBMS > Amazon Redshift vs. Axibase vs. Geode vs. HEAVY.AI vs. Kinetica

System Properties Comparison Amazon Redshift vs. Axibase vs. Geode vs. HEAVY.AI vs. Kinetica

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

Primary database model

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series 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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

geode.apache.org

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

Technical documentation

docs.aws.amazon.com/redshift

geode.apache.org/docs

docs.heavy.ai

docs.kinetica.com

Developer

Amazon (based on PostgreSQL)

Axibase Corporation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

HEAVY.AI, Inc.

Kinetica

Initial release

2012

2013

2002

2016

2012

Current release

15585

1.1, February 2017

5.10, January 2022

7.1, August 2021

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 as Gemfire

Open Source

Apache Version 2; enterprise edition available

commercial

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++ and CUDA

C, C++

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

SQL-like query language (OQL)

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

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

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

yes, on a single node

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.