DBMS > GeoMesa vs. GridGain vs. Heroic vs. TimescaleDB

System Properties Comparison GeoMesa vs. GridGain vs. Heroic vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

GridGain is an in-memory computing platform, built on Apache Ignite

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Spatial DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

www.geomesa.org

www.gridgain.com

github.com/spotify/heroic

www.timescale.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

www.gridgain.com/docs/index.html

spotify.github.io/heroic

docs.timescale.com

Developer

CCRi and others

GridGain Systems, Inc.

Spotify

Timescale

Initial release

2014

2007

2014

2017

Current release

5.0.1, July 2024

GridGain 8.5.1

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial, open source

Open Source

Apache 2.0

Open Source

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

Scala

Java, C++, .Net, Python, REST, SQL

Java

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

ANSI-99 for query and DML statements, subset of DDL

yes

full PostgreSQL SQL syntax

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control
Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

GridGain Advances Its Unified Real-Time Data Platform to Help Enterprises Accelerate AI-Driven Data Processing
10 July 2024, insideainews.com

GridGain Sponsoring Strategic AI and Kafka Conferences This Month
4 September 2024, Datanami

GridGain in-memory data and generative AI
10 May 2024, Blocks & Files

Data Management News for the Week of July 12; Updates from Cloudera, HerculesAI, Oracle & More
12 July 2024, Solutions Review

Lalit Ahuja
13 August 2024, Forbes

provided by Google News

General availability: Latest version of the TimeScaleDB extension on Azure Database for PostgreSQL - Flexible Server
8 May 2024, Microsoft

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

PostgreSQL is Now Faster than Pinecone, 75% Cheaper, with New Open Source Extensions
11 June 2024, PR Newswire

Understanding Hyperfunctions in TimescaleDB
11 August 2021, CDOTrends

provided by Google News

Share this page