DBMS > Dolt vs. IBM Db2 Event Store vs. KairosDB vs. SAP HANA

System Properties Comparison Dolt vs. IBM Db2 Event Store vs. KairosDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Distributed Event Store optimized for Internet of Things use cases

Distributed Time Series DBMS based on Cassandra or H2

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

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

github.com/kairosdb/kairosdb

www.sap.com/products/hana.html

Technical documentation

docs.dolthub.com

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

kairosdb.github.io

help.sap.com/hana

Developer

DoltHub Inc

IBM

SAP

Initial release

2018

2017

2013

2010

Current release

2.0

1.2.2, November 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free developer edition available

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Java

Server operating systems

Linux
macOS
Windows

Linux

Linux, macOS, Windows for the developer addition

Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Active-active shard replication

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

simple password-based access control

yes

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.