DBMS > H2 vs. IBM Db2 Event Store vs. IRONdb vs. Microsoft Azure Cosmos DB

System Properties Comparison H2 vs. IBM Db2 Event Store vs. IRONdb vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

Distributed Event Store optimized for Internet of Things use cases

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

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

Website

www.h2database.com

www.ibm.com/products/db2-event-store

www.circonus.com/solutions/time-series-database/

azure.microsoft.com/services/cosmos-db

Technical documentation

www.h2database.com/html/main.html

www.ibm.com/docs/en/db2-event-store

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

Developer

Thomas Mueller

IBM

Circonus LLC.

Microsoft

Initial release

2005

2017

2014

Current release

2.2.220, July 2023

2.0

V0.10.20, January 2018

License

Commercial or Open Source

Open Source

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

commercial

free developer edition 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

C and C++

Server operating systems

All OS with a Java VM

Linux

Linux, macOS, Windows for the developer addition

Linux

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

through the embedded Spark runtime

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

JDBC
ODBC

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

HTTP API

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

Supported programming languages

Java

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

yes, in Lua

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

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

Active-active shard replication

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

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

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

In-memory capabilities

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

yes

User concepts

Access control

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.