DBMS > EventStoreDB vs. GeoMesa vs. H2 vs. Microsoft Azure Cosmos DB vs. XTDB

System Properties Comparison EventStoreDB vs. GeoMesa vs. H2 vs. Microsoft Azure Cosmos DB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Globally distributed, horizontally scalable, multi-model database service

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Event Store

Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

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

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.eventstore.com

www.geomesa.org

www.h2database.com

azure.microsoft.com/services/cosmos-db

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developers.eventstore.com

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

www.h2database.com/html/main.html

learn.microsoft.com/azure/cosmos-db

www.xtdb.com/docs

Developer

Event Store Limited

CCRi and others

Thomas Mueller

Microsoft

Juxt Ltd.

Initial release

2012

2014

2005

2014

2019

Current release

21.2, February 2021

5.0.0, May 2024

2.2.220, July 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Open Source

MIT License

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

Scala

Java

Clojure

Server operating systems

Linux
Windows

All OS with a Java VM

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes, extensible-data-notation format

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

yes

SQL

Support of SQL

yes

SQL-like query language

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

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

HTTP REST
JDBC

Supported programming languages

Java

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

Clojure
Java

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

Implicit feature of the cloud service

yes, each node contains all data

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.