DBMS > GeoMesa vs. IRONdb vs. RRDtool vs. WakandaDB

System Properties Comparison GeoMesa vs. IRONdb vs. RRDtool vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb 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.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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.

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Spatial DBMS

Time Series DBMS

Object oriented DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

www.circonus.com/solutions/time-series-database/

oss.oetiker.ch/rrdtool

wakanda.github.io

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

oss.oetiker.ch/rrdtool/doc

wakanda.github.io/doc

Developer

CCRi and others

Circonus LLC.

Tobias Oetiker

Wakanda SAS

Initial release

2014

2017

1999

2012

Current release

4.0.5, February 2024

V0.10.20, January 2018

1.8.0, 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL V2 and FLOSS

Open Source

AGPLv3, extended commercial license available

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

Scala

C and C++

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

C++, JavaScript

Server operating systems

Linux

HP-UX
Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

HTTP API

in-process shared library
Pipes

RESTful HTTP API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

JavaScript

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

configurable replication factor, datacenter aware

none

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

Immediate consistency per node, eventual consistency across nodes

none

Immediate Consistency

Foreign keys

Referential integrity

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

User concepts

Access control

yes

depending on the DBMS used for storage

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.

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

SQLi vulnerability in Cacti could lead to RCE (CVE-2023-51448)
9 January 2024, Help Net Security

Critical IP spoofing bug patched in Cacti
15 December 2022, The Daily Swig

Cacti: Using Graphs to Monitor Networks and Devices
16 March 2011, Packt Hub

A plotting utility for text mode consoles and terminals @tenox77
28 June 2023, Adafruit Blog

How to install Cacti SNMP Monitor on Ubuntu
24 November 2017, TechRepublic

provided by Google News

Share this page