DBMS > Amazon Redshift vs. Hazelcast vs. MonetDB vs. RavenDB

System Properties Comparison Amazon Redshift vs. Hazelcast vs. MonetDB vs. RavenDB

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

A widely adopted in-memory data grid

A relational database management system that stores data in columns

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Graph 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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

hazelcast.com

www.monetdb.org

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

www.monetdb.org/Documentation

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Hazelcast

MonetDB BV

Hibernating Rhinos

Initial release

2012

2008

2004

2010

Current release

5.3.6, November 2023

Dec2023 (11.49), December 2023

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Mozilla Public License 2.0

Open Source

AGPL version 3, commercial license 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

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

yes

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

yes

SQL 2003 with some extensions

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

yes, in SQL, C, R

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

Source-replica replication available in experimental status

Multi-source 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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

Authorization levels configured per client per database

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.