DBMS > GridDB vs. Heroic vs. MySQL vs. OpenTenBase

System Properties Comparison GridDB vs. Heroic vs. MySQL vs. OpenTenBase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

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

Widely used open source RDBMS

An enterprise-level distributed HTAP open source database based on PostgreSQL

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Document store
Spatial DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

griddb.net

github.com/spotify/heroic

www.mysql.com

github.com/OpenTenBase/OpenTenBase
www.opentenbase.org

Technical documentation

docs.griddb.net

spotify.github.io/heroic

dev.mysql.com/doc

docs.opentenbase.org
docs.opentenbase.org/en

Developer

Toshiba Corporation

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

OpenAtom Foundation, previously Tencent

Initial release

2013

2014

1995

Current release

5.1, August 2022

9.0.0, July 2024

2.5, January 2024

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-3

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

C++

Java

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

C
Go
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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

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 at container level

ACID

not for MyISAM storage engine

ACID

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

User concepts

Access control

Access rights for users can be defined per database

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.