DBMS > Blueflood vs. GeoMesa vs. Hawkular Metrics vs. PostGIS vs. TimescaleDB

System Properties Comparison Blueflood vs. GeoMesa vs. Hawkular Metrics vs. PostGIS vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Spatial extension of PostgreSQL

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

Primary database model

Secondary database models

Relational DBMS

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

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.87
Rank	#74	Overall
	#4	Time Series DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

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

www.hawkular.org/hawkular-metrics/docs/user-guide

postgis.net/documentation

docs.timescale.com

Developer

Rackspace

CCRi and others

Community supported by Red Hat

Timescale

Initial release

2013

2014

2005

2017

Current release

4.0.5, February 2024

3.4.2, February 2024

2.13.0, November 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL v2.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

Java

Scala

Java

Server operating systems

Linux
OS X

Linux
OS X
Windows

Data scheme

predefined 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

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP REST

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

Supported programming languages

Go
Java
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

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

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

depending on storage layer

Sharding

based on Cassandra

yes

based on PostgreSQL

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

depending on storage layer

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

User concepts

Access control

yes

depending on the DBMS used for storage

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

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

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

Timescale Announces Corporate Rebrand Reflecting Company's Growth
17 May 2023, PR Newswire

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

provided by Google News

Share this page