DBMS > Amazon Redshift vs. Apache Drill vs. Hazelcast vs. UniData,UniVerse

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Hazelcast vs. UniData,UniVerse

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A widely adopted in-memory data grid

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Relational DBMS

Document store
Relational DBMS

Key-value store

Multivalue DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

aws.amazon.com/redshift

drill.apache.org

hazelcast.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

hazelcast.org/imdg/docs

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Hazelcast

Rocket Software

Initial release

2012

2008

1985

Current release

1.20.3, January 2023

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

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

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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 SELECT statement is SQL:2003 compliant

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

All languages supporting JDBC/ODBC

C++

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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

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

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Role-based access control

Access rights according to SQL-standard and operating system based

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.