DBMS > Hazelcast vs. Microsoft Azure Data Explorer vs. MySQL vs. SWC-DB vs. TimescaleDB

System Properties Comparison Hazelcast vs. Microsoft Azure Data Explorer vs. MySQL vs. SWC-DB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A high performance, scalable Wide Column DBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Key-value store

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Wide column store

Time Series 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
Spatial DBMS

Time Series DBMS

Relational DBMS

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

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

hazelcast.com

azure.microsoft.com/services/data-explorer

www.mysql.com

github.com/kashirin-alex/swc-db
www.swcdb.org

www.timescale.com

Technical documentation

hazelcast.org/imdg/docs

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

dev.mysql.com/doc

docs.timescale.com

Developer

Hazelcast

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Alex Kashirin

Timescale

Initial release

2008

2019

1995

2020

2017

Current release

5.3.6, November 2023

cloud service with continuous releases

9.0.0, July 2024

0.5, April 2021

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

Open Source

Apache 2.0

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

C++

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

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

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol
Thrift

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

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

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

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

Multi-source replication
Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.