DBMS > GeoSpock vs. HEAVY.AI vs. Lovefield vs. Microsoft Azure Data Explorer vs. MySQL

System Properties Comparison GeoSpock vs. HEAVY.AI vs. Lovefield vs. Microsoft Azure Data Explorer vs. MySQL

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Embeddable relational database for web apps written in pure JavaScript

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

Spatial 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	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

geospock.com

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

azure.microsoft.com/services/data-explorer

www.mysql.com

Technical documentation

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

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

dev.mysql.com/doc

Developer

GeoSpock

HEAVY.AI, Inc.

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2014

2019

1995

Current release

2.0, September 2019

5.10, January 2022

2.1.12, February 2017

cloud service with continuous releases

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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 CUDA

JavaScript

C and C++

Server operating systems

hosted

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

FreeBSD
Linux
OS X
Solaris
Windows

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

yes

all fields are automatically indexed

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

via JavaScript builder pattern

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

JDBC

JDBC
ODBC
Thrift
Vega

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

.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

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

Using read-only observers

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

Round robin

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

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

Multi-source replication
Source-replica replication

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

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

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

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.