DBMS > Coveo vs. IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. MySQL vs. Prometheus

System Properties Comparison Coveo vs. IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. MySQL vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Distributed Event Store optimized for Internet of Things use cases

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Search engine

Event Store
Time Series DBMS

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

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	2.28
Rank	#114	Overall
	#11	Search engines

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	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

www.coveo.com

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

azure.microsoft.com/services/data-explorer

www.mysql.com

prometheus.io

Technical documentation

docs.coveo.com

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

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

dev.mysql.com/doc

prometheus.io/docs

Developer

Coveo

IBM

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2017

2019

1995

2015

Current release

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

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.

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

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

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/JSON API

Supported programming languages

C#
Java
JavaScript
Python

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

yes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

yes

by Federation

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

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

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

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.