DBMS > Heroic vs. NSDb vs. OrigoDB vs. Transbase vs. XTDB

System Properties Comparison Heroic vs. NSDb vs. OrigoDB vs. Transbase 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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

A resource-optimized, high-performance, universally applicable RDBMS

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

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Document store

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/spotify/heroic

nsdb.io

origodb.com

www.transaction.de/en/products/transbase.html

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

Technical documentation

spotify.github.io/heroic

nsdb.io/Architecture

origodb.com/docs

www.transaction.de/en/products/transbase/features.html

www.xtdb.com/docs

Developer

Spotify

Robert Friberg et al

Transaction Software GmbH

Juxt Ltd.

Initial release

2014

2017

2009

under the name LiveDB

1987

2019

Current release

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

commercial

free development license

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Java, Scala

C and C++

Clojure

Server operating systems

Linux
macOS

Linux
Windows

FreeBSD
Linux
macOS
Solaris
Windows

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

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

Java
Scala

.Net

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Eventual 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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page