DBMS > H2 vs. KairosDB vs. RavenDB vs. SAP HANA vs. ToroDB

System Properties Comparison H2 vs. KairosDB vs. RavenDB vs. SAP HANA vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB 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 Time Series DBMS based on Cassandra or H2

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.h2database.com

github.com/kairosdb/kairosdb

ravendb.net

www.sap.com/products/hana.html

github.com/torodb/server

Technical documentation

www.h2database.com/html/main.html

kairosdb.github.io

ravendb.net/docs

help.sap.com/hana

Developer

Thomas Mueller

Hibernating Rhinos

SAP

8Kdata

Initial release

2005

2013

2010

2016

Current release

2.2.220, July 2023

1.2.2, November 2018

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

commercial

Open Source

AGPL-V3

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

Java

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java

Java
JavaScript

Node.js
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

yes

Sharding

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

selectable replication factor

based on Cassandra

Multi-source replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

Authorization levels configured per client per database

yes

Access rights for users and roles

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.