DBMS > Heroic vs. PostGIS

System Properties Comparison Heroic vs. PostGIS

Please select another system to include it in the comparison.

Our visitors often compare Heroic and PostGIS with Databricks.

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

Primary database model

Time Series DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/spotify/heroic

postgis.net

Technical documentation

spotify.github.io/heroic

postgis.net/documentation

Developer

Spotify

Initial release

2014

2005

Current release

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

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

Java

Data scheme

schema-free

yes

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

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

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.

User concepts

Access control

yes

based on PostgreSQL

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.