DBMS > Apache Phoenix vs. GeoMesa vs. Hawkular Metrics vs. Postgres-XL vs. SAP HANA

System Properties Comparison Apache Phoenix vs. GeoMesa vs. Hawkular Metrics vs. Postgres-XL vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

phoenix.apache.org

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

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

www.postgres-xl.org/documentation

help.sap.com/hana

Developer

Apache Software Foundation

CCRi and others

Community supported by Red Hat

SAP

Initial release

2014

since 2012, originally named StormDB

2010

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

5.0.0, May 2024

10 R1, October 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Mozilla public license

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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
Unix
Windows

Linux
OS X
Windows

Linux
macOS

Appliance or cloud-service

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC

HTTP REST

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

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Go
Java
Python
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

based on Cassandra

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

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

MVCC

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.

yes

depending on storage layer

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

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.