DBMS > Amazon Redshift vs. Apache IoTDB vs. Blueflood vs. Hazelcast

System Properties Comparison Amazon Redshift vs. Apache IoTDB vs. Blueflood vs. Hazelcast

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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Scalable TimeSeries DBMS based on Cassandra

A widely adopted in-memory data grid

Primary database model

Relational DBMS

Time Series 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.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

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

Website

aws.amazon.com/redshift

iotdb.apache.org

blueflood.io

hazelcast.com

Technical documentation

docs.aws.amazon.com/redshift

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

github.com/rax-maas/blueflood/wiki

hazelcast.org/imdg/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Rackspace

Hazelcast

Initial release

2012

2018

2013

2008

Current release

1.1.0, April 2023

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses 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

All OS with a Java VM (>= 1.8)

Linux
OS X

All OS with a Java VM

Data scheme

yes

predefined scheme

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.

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
Native API

HTTP REST

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
Python
Scala

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

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 time range) + vertical partitioning (by deviceId)

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

selectable replication factor

based on Cassandra

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

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

yes

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.