DBMS > Heroic vs. TempoIQ vs. TerarkDB vs. Tkrzw

System Properties Comparison Heroic vs. TempoIQ vs. TerarkDB vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

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 concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Key-value 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
	#60	Key-value stores

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

Website

github.com/spotify/heroic

tempoiq.com (offline)

github.com/bytedance/terarkdb

dbmx.net/tkrzw

Technical documentation

spotify.github.io/heroic

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Spotify

TempoIQ

ByteDance, originally Terark

Mikio Hirabayashi

Initial release

2014

2012

2016

2020

Current release

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted open source version available

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

Linux
macOS

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

APIs and other access methods

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

HTTP API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript

Node.js
Python
Ruby

C++
Java

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

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

using specific database classes

User concepts

Access control

simple authentication-based access control

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