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

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

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

Vector DBMS

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	16.36
Rank	#37	Overall
	#4	Search engines

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

github.com/opensearch-project
opensearch.org

github.com/bytedance/terarkdb

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

Technical documentation

spotify.github.io/heroic

docs.kinetica.com

opensearch.org/docs/latest

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.xtdb.com/docs

Developer

Spotify

Kinetica

Amazon Web Services

ByteDance, originally Terark

Juxt Ltd.

Initial release

2014

2012

2021

2016

2019

Current release

7.1, August 2021

2.5.0, January 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

C, C++

Java

C++

Clojure

Server operating systems

Linux

All OS with a Java VM

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

Data scheme

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

via Elasticsearch

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

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

Java API
RESTful HTTP/JSON API

C++ API
Java API

HTTP REST
JDBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C++
Java

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

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

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

none

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 or Eventual Consistency depending on configuration

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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

User concepts

Access control

Access rights for users and roles on table level

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.