DBMS > Heroic vs. Kinetica vs. Oracle vs. TerarkDB vs. XTDB

System Properties Comparison Heroic vs. Kinetica vs. Oracle vs. TerarkDB 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

Fully vectorized database across both GPUs and CPUs

Widely used RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/spotify/heroic

www.kinetica.com

www.oracle.com/database

github.com/bytedance/terarkdb

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

Technical documentation

spotify.github.io/heroic

docs.kinetica.com

docs.oracle.com/en/database

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.xtdb.com/docs

Developer

Spotify

Kinetica

Oracle

ByteDance, originally Terark

Juxt Ltd.

Initial release

2014

2012

1980

2016

2019

Current release

7.1, August 2021

23c, September 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

restricted open source version available

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

C, C++

C and C++

C++

Clojure

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

C++ API
Java API

HTTP REST
JDBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++
Java

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

GPU vRAM or System RAM

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Access rights for users and roles on table level

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.