DBMS > EXASOL vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. SiriDB vs. TigerGraph

System Properties Comparison EXASOL vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. SiriDB vs. TigerGraph

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

Globally distributed, horizontally scalable, multi-model database service

Open Source Time Series DBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Graph DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

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

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.exasol.com

hazelcast.com

azure.microsoft.com/services/cosmos-db

siridb.com

www.tigergraph.com

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

docs.siridb.com

docs.tigergraph.com

Developer

Exasol

Hazelcast

Microsoft

Cesbit

Initial release

2000

2008

2014

2017

Current release

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

MIT License

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++

Server operating systems

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

Numeric data

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

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Java
Lua
Python
R

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

JavaScript

yes

Triggers

yes

Events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

one or two-phase-commit; repeatable reads; read commited

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

simple rights management via user accounts

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.