DBMS > GeoMesa vs. Heroic vs. RRDtool vs. SAP Advantage Database Server vs. SAP HANA

System Properties Comparison GeoMesa vs. Heroic vs. RRDtool vs. SAP Advantage Database Server vs. SAP HANA

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.geomesa.org

github.com/spotify/heroic

oss.oetiker.ch/rrdtool

www.sap.com/products/advantage-database-server.html

www.sap.com/products/hana.html

Technical documentation

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

spotify.github.io/heroic

oss.oetiker.ch/rrdtool/doc

help.sap.com/hana

Developer

CCRi and others

Spotify

Tobias Oetiker

Sybase, SAP

SAP

Initial release

2014

1999

1993

2010

Current release

5.0.0, May 2024

1.8.0, 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL V2 and FLOSS

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

Scala

Java

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

HP-UX
Linux

Linux
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

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

in-process shared library
Pipes

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Immediate Consistency

none

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

by using the rrdcached daemon

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

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.