DBMS > GeoSpock vs. Heroic vs. Snowflake vs. TempoIQ

System Properties Comparison GeoSpock vs. Heroic vs. Snowflake vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

Spatial and temporal data processing engine for extreme data scale

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

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

geospock.com

github.com/spotify/heroic

www.snowflake.com

tempoiq.com (offline)

Technical documentation

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

Spotify

Snowflake Computing Inc.

TempoIQ

Initial release

2014

2012

Current release

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.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, Javascript

Java

Server operating systems

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

temporal, categorical

yes

via Elasticsearch

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

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

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Access rights for users can be defined per table

Users with fine-grained authorization concept, user roles and pluggable authentication

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.