DBMS > EXASOL vs. Hazelcast vs. IBM Db2 vs. Snowflake

System Properties Comparison EXASOL vs. Hazelcast vs. IBM Db2 vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A widely adopted in-memory data grid

Common in IBM host environments, 2 different versions for host and Windows/Linux

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

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

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.exasol.com

hazelcast.com

www.ibm.com/products/db2

www.snowflake.com

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

www.ibm.com/docs/en/db2

docs.snowflake.net/manuals/index.html

Developer

Exasol

Hazelcast

IBM

Snowflake Computing Inc.

Initial release

2000

2008

1983

host version

2014

Current release

5.3.6, November 2023

12.1, October 2016

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

free version is 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 C++

Server operating systems

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows
z/OS

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

yes

user defined functions

Triggers

yes

Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

with separate tools (MQ, InfoSphere)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

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

Access rights for users, groups and roles according to SQL-standard

Role-based access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.