DBMS > Hazelcast vs. Ignite vs. Microsoft Azure Data Explorer vs. SAP HANA vs. Yaacomo

System Properties Comparison Hazelcast vs. Ignite vs. Microsoft Azure Data Explorer vs. SAP HANA vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A widely adopted in-memory data grid

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Fully managed big data interactive analytics platform

In-memory, column based data store. Available as appliance or cloud service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

hazelcast.com

ignite.apache.org

azure.microsoft.com/services/data-explorer

www.sap.com/products/hana.html

yaacomo.com

Technical documentation

hazelcast.org/imdg/docs

apacheignite.readme.io/docs

docs.microsoft.com/en-us/azure/data-explorer

help.sap.com/hana

Developer

Hazelcast

Apache Software Foundation

Microsoft

SAP

Q2WEB GmbH

Initial release

2008

2015

2019

2010

2009

Current release

5.3.6, November 2023

Apache Ignite 2.6

cloud service with continuous releases

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++, Java, .Net

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

hosted

Appliance or cloud-service

Android
Linux
Windows

Data scheme

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes (compute grid and cache interceptors can be used instead)

Yes, possible languages: KQL, Python, R

SQLScript, R

Triggers

yes

Events

yes (cache interceptors and events)

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes (replicated cache)

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Role-based access control

Security Hooks for custom implementations

Azure Active Directory Authentication

yes

fine grained access rights according to SQL-standard

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.