DBMS > Heroic vs. LevelDB vs. OrigoDB vs. SAP HANA vs. XTDB

System Properties Comparison Heroic vs. LevelDB vs. OrigoDB vs. SAP HANA vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A fully ACID in-memory object graph database

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

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

Primary database model

Time Series DBMS

Key-value store

Document store
Object oriented DBMS

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/spotify/heroic

github.com/google/leveldb

origodb.com

www.sap.com/products/hana.html

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

Technical documentation

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

origodb.com/docs

help.sap.com/hana

www.xtdb.com/docs

Developer

Spotify

Google

Robert Friberg et al

SAP

Juxt Ltd.

Initial release

2014

2011

2009

under the name LiveDB

2010

2019

Current release

1.23, February 2021

2.0 SPS07 (April 4, 2023), April 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

commercial

Open Source

MIT License

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

C++

Clojure

Server operating systems

Illumos
Linux
OS X
Windows

Linux
Windows

Appliance or cloud-service

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

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.

can be achieved using .NET

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net

Clojure
Java

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

Write ahead log

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.

yes

User concepts

Access control

Role based authorization

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.