DBMS > GeoMesa vs. jBASE vs. OrigoDB vs. RRDtool

System Properties Comparison GeoMesa vs. jBASE vs. OrigoDB vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A robust multi-value DBMS comprising development tools and middleware

A fully ACID in-memory object graph database

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.

Primary database model

Spatial DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

origodb.com

oss.oetiker.ch/rrdtool

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

origodb.com/docs

oss.oetiker.ch/rrdtool/doc

Developer

CCRi and others

Rocket Software (formerly Zumasys)

Robert Friberg et al

Tobias Oetiker

Initial release

2014

1991

2009

under the name LiveDB

1999

Current release

4.0.5, February 2024

5.7

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL V2 and FLOSS

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

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

Server operating systems

AIX
Linux
Windows

Linux
Windows

HP-UX
Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

User defined using .NET types and collections

Numeric data only

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

can be achieved using .NET

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

.NET Client API
HTTP API
LINQ

in-process shared library
Pipes

Supported programming languages

.Net
Basic
Jabbascript
Java

.Net

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

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Source-replica replication

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

none

Foreign keys

Referential integrity

depending on model

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

Durability

Support for making data persistent

yes

Write ahead log

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

Access rights can be defined down to the item level

Role based authorization

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

Temenos signs first customer in India
24 August 2009, Finextra

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

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

Installation Guide for Collectd and Collectd-Web to Monitor Server Resources in Linux
29 November 2017, Linux.com

Cacti servers under attack by attackers exploiting CVE-2022-46169
16 January 2023, Help Net Security

provided by Google News

Share this page