DBMS > eXtremeDB vs. GridDB vs. Microsoft Azure Data Explorer vs. MySQL vs. Tkrzw

System Properties Comparison eXtremeDB vs. GridDB vs. Microsoft Azure Data Explorer vs. MySQL vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Natively in-memory DBMS with options for persistency, high-availability and clustering

Scalable in-memory time series database optimized for IoT and Big Data

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS
Time Series DBMS

Time Series DBMS

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Key-value store
Relational DBMS

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

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

Score	0.80
Rank	#214	Overall
	#99	Relational DBMS
	#18	Time Series DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.mcobject.com

griddb.net

azure.microsoft.com/services/data-explorer

www.mysql.com

dbmx.net/tkrzw

Technical documentation

www.mcobject.com/docs/extremedb.htm

docs.griddb.net

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

dev.mysql.com/doc

Developer

McObject

Toshiba Corporation

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Mikio Hirabayashi

Initial release

2001

2013

2019

1995

2020

Current release

8.2, 2021

5.1, August 2022

cloud service with continuous releases

8.4.0, April 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

C and C++

C++

Server operating systems

AIX
HP-UX
Linux
macOS
Solaris
Windows

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

support of XML interfaces available

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

SQL92, SQL-like TQL (Toshiba Query Language)

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C#
C++
Java
Lua
Python
Scala

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

.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++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

yes

by defining events

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning / sharding

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Source-replica replication

yes

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

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at container level

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

using specific database classes

User concepts

Access control

Access rights for users can be defined per database

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

GitHub trending repository
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» more

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.