DBMS > EsgynDB vs. GeoMesa vs. Google BigQuery vs. Microsoft Azure Data Explorer vs. ToroDB

System Properties Comparison EsgynDB vs. GeoMesa vs. Google BigQuery vs. Microsoft Azure Data Explorer vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Large scale data warehouse service with append-only tables

Fully managed big data interactive analytics platform

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

column oriented

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

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Website

www.esgyn.cn

www.geomesa.org

cloud.google.com/bigquery

azure.microsoft.com/services/data-explorer

github.com/torodb/server

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/bigquery/docs

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

Developer

Esgyn

CCRi and others

Google

Microsoft

8Kdata

Initial release

2015

2014

2010

2019

2016

Current release

4.0.5, February 2024

cloud service with continuous releases

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

AGPL-V3

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

C++, Java

Scala

Java

Server operating systems

Linux

hosted

All OS with a Java 7 VM

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

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

string, integer, double, boolean, date, object_id

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

yes

all fields are automatically indexed

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

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

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

Yes, possible languages: KQL, Python, R

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

depending on storage layer

yes

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

Source-replica replication

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

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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.

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Azure Active Directory Authentication

Access rights for users and 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.