DBMS > Heroic vs. MySQL vs. OpenTSDB vs. Sadas Engine

System Properties Comparison Heroic vs. MySQL vs. OpenTSDB vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Scalable Time Series DBMS based on HBase

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

github.com/spotify/heroic

www.mysql.com

opentsdb.net

www.sadasengine.com

Technical documentation

spotify.github.io/heroic

dev.mysql.com/doc

opentsdb.net/docs/build/html/index.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

currently maintained by Yahoo and other contributors

SADAS s.r.l.

Initial release

2014

1995

2011

2006

Current release

8.4.0, April 2024

8.0

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

LGPL

commercial

free trial version available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

AIX
Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Telnet API

JDBC
ODBC
Proprietary protocol

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Erlang
Go
Java
Python
R
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

managed by 'Learn by Usage'

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles 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.