DBMS > Amazon Redshift vs. Hazelcast vs. Heroic vs. Kyligence Enterprise vs. Trafodion

System Properties Comparison Amazon Redshift vs. Hazelcast vs. Heroic vs. Kyligence Enterprise vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted in-memory data grid

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

A distributed analytics engine for big data, built on top of Apache Kylin

Transactional SQL-on-Hadoop DBMS

Primary database model

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	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Website

aws.amazon.com/redshift

hazelcast.com

github.com/spotify/heroic

kyligence.io/kyligence-enterprise

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

spotify.github.io/heroic

trafodion.apache.org/documentation.html

Developer

Amazon (based on PostgreSQL)

Hazelcast

Spotify

Kyligence, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2012

2008

2014

2016

2014

Current release

5.3.6, November 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

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

C++, Java

Server operating systems

hosted

All OS with a Java VM

Linux

Data scheme

yes

schema-free

yes

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.

yes

the object must implement a serialization strategy

Secondary indexes

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

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

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

Java Stored Procedures

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

ACID

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

fine grained access rights according to SQL-standard

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.