DBMS > Hawkular Metrics vs. PostGIS vs. Tkrzw vs. VoltDB vs. XTDB

System Properties Comparison Hawkular Metrics vs. PostGIS vs. Tkrzw vs. VoltDB 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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational 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

docs.voltdb.com

www.xtdb.com/docs

Developer

Community supported by Red Hat

Mikio Hirabayashi

VoltDB Inc.

Juxt Ltd.

Initial release

2014

2005

2020

2010

2019

Current release

3.4.2, February 2024

0.9.3, August 2020

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

Java, C++

Clojure

Server operating systems

Linux
OS X
Windows

Linux
macOS

Linux
OS X

for development

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

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

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP REST

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

Go
Java
Python
Ruby

C++
Java
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

yes

based on PostgreSQL

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

using specific database classes

User concepts

Access control

yes

based on PostgreSQL

Users and roles with access to stored procedures

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

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

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page