DBMS > Hawkular Metrics vs. PostGIS vs. RocksDB vs. TimescaleDB vs. XTDB

System Properties Comparison Hawkular Metrics vs. PostGIS vs. RocksDB vs. TimescaleDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

postgis.net/documentation

github.com/facebook/rocksdb/wiki

docs.timescale.com

www.xtdb.com/docs

Developer

Community supported by Red Hat

Facebook, Inc.

Timescale

Juxt Ltd.

Initial release

2014

2005

2013

2017

2019

Current release

3.4.2, February 2024

8.11.4, April 2024

2.13.0, November 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

BSD

Open Source

Apache 2.0

Open Source

MIT License

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

C++

Clojure

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

yes

schema-free

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

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP REST

C++ API
Java API

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

HTTP REST
JDBC

Supported programming languages

Go
Java
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java

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

yes

based on PostgreSQL

horizontal partitioning

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

yes

Source-replica replication with hot standby and reads on replicas

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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.