DBMS > Drizzle vs. GeoMesa vs. Microsoft Azure Cosmos DB vs. Yanza

System Properties Comparison Drizzle vs. GeoMesa vs. Microsoft Azure Cosmos DB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

yanza.com

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Microsoft

Yanza

Initial release

2008

2014

2015

Current release

7.2.4, September 2012

5.0.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Scala

Server operating systems

FreeBSD
Linux
OS X

hosted

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC

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

HTTP API

Supported programming languages

C
C++
Java
PHP

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

Triggers

hooks for callbacks inside the server can be used.

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.