DBMS > Geode vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Yaacomo

System Properties Comparison Geode vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Relational DBMS

Secondary database models

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

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Website

geode.apache.org

machbase.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

yaacomo.com

Technical documentation

geode.apache.org/docs

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

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

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Machbase

Microsoft

Q2WEB GmbH

Initial release

2002

2013

2014

2019

2009

Current release

1.1, February 2017

V8.0, August 2023

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free test version 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.

Implementation language

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Windows

hosted

Android
Linux
Windows

Data scheme

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

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

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

user defined functions

JavaScript

Yes, possible languages: KQL, Python, R

Triggers

yes

Cache Event Listeners

JavaScript

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes

Implicit feature of the cloud service

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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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.

yes

volatile and lookup table

yes

User concepts

Access control

Access rights per client and object definable

simple password-based access control

Access rights can be defined down to the item level

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

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.