DBMS > Heroic vs. Interbase vs. SAP HANA vs. TerarkDB

System Properties Comparison Heroic vs. Interbase vs. SAP HANA vs. TerarkDB

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

Light-weight proven RDBMS

originally from Borland

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

github.com/spotify/heroic

www.embarcadero.com/products/interbase

www.sap.com/products/hana.html

github.com/bytedance/terarkdb

Technical documentation

spotify.github.io/heroic

docs.embarcadero.com/products/interbase

help.sap.com/hana

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Spotify

Embarcadero

SAP

ByteDance, originally Terark

Initial release

2014

1984

2010

2016

Current release

InterBase 2020, December 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

Android
iOS
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

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.

export as XML data possible

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C++
Java

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Interbase Change Views

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

yes

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.