DBMS > Heroic vs. PostGIS vs. SAP HANA vs. Tkrzw

System Properties Comparison Heroic vs. PostGIS vs. SAP HANA vs. Tkrzw

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

Spatial extension of PostgreSQL

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

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

Secondary database models

Relational DBMS

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.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

github.com/spotify/heroic

postgis.net

www.sap.com/products/hana.html

dbmx.net/tkrzw

Technical documentation

spotify.github.io/heroic

postgis.net/documentation

help.sap.com/hana

Developer

Spotify

SAP

Mikio Hirabayashi

Initial release

2014

2005

2010

2020

Current release

3.4.2, February 2024

2.0 SPS07 (April 4, 2023), April 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

commercial

Open Source

Apache Version 2.0

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

Appliance or cloud-service

Linux
macOS

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.

yes

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

JDBC
ODBC

Supported programming languages

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

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

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

yes

based on PostgreSQL

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.