DBMS > GeoSpock vs. IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. MySQL vs. SpaceTime

System Properties Comparison GeoSpock vs. IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. MySQL vs. SpaceTime

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Distributed Event Store optimized for Internet of Things use cases

Fully managed big data interactive analytics platform

Widely used open source RDBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

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

Relational DBMS

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

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

geospock.com

www.ibm.com/products/db2-event-store

azure.microsoft.com/services/data-explorer

www.mysql.com

www.mireo.com/spacetime

Technical documentation

www.ibm.com/docs/en/db2-event-store

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

dev.mysql.com/doc

Developer

GeoSpock

IBM

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Mireo

Initial release

2017

2019

1995

2020

Current release

2.0, September 2019

2.0

cloud service with continuous releases

8.4.0, April 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

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

Implementation language

Java, Javascript

C and C++

C++

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

Secondary indexes

temporal, categorical

all fields are automatically indexed

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

through the embedded Spark runtime

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.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#
C++
Python

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

yes

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

Multi-source replication
Source-replica replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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 can be defined per table

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

yes

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.