DBMS > Heroic vs. PostGIS vs. searchxml vs. TempoIQ

System Properties Comparison Heroic vs. PostGIS vs. searchxml vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

Spatial extension of PostgreSQL

DBMS for structured and unstructured content wrapped with an application server

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Time Series DBMS

Spatial DBMS

Native XML DBMS
Search engine

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

github.com/spotify/heroic

postgis.net

www.searchxml.net/category/products

tempoiq.com (offline)

Technical documentation

spotify.github.io/heroic

postgis.net/documentation

www.searchxml.net/support/handouts

Developer

Spotify

informationpartners gmbh

TempoIQ

Initial release

2014

2005

2015

2012

Current release

3.4.2, February 2024

1.0

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

Windows

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

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP API

Supported programming languages

C++

most other programming languages supported via APIs

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

yes

sychronisation to multiple collections

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

multiple readers, single writer

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

Domain, group and role-based access control at the document level and for application services

simple authentication-based access control

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.