DBMS > Bangdb vs. Geode vs. MySQL vs. RavenDB vs. RRDtool

System Properties Comparison Bangdb vs. Geode vs. MySQL vs. RavenDB vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document 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

Document store
Graph DBMS
Time Series DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

oss.oetiker.ch/rrdtool

Technical documentation

docs.bangdb.com

geode.apache.org/docs

dev.mysql.com/doc

ravendb.net/docs

oss.oetiker.ch/rrdtool/doc

Developer

Sachin Sinha, BangDB

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Tobias Oetiker

Initial release

2012

2002

1995

2010

1999

Current release

BangDB 2.0, October 2021

1.1, February 2017

8.4.0, April 2024

5.4, July 2022

1.8.0, 2022

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++

Java

C and C++

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

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (OQL)

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

Proprietary protocol
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

in-process shared library
Pipes

Supported programming languages

C
C#
C++
Java
Python

.Net
All JVM based languages
C++
Groovy
Java
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

user defined functions

yes

proprietary syntax

yes

Triggers

yes, Notifications (with Streaming only)

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Eventual Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes, on a single node

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

table locks or row locks depending on storage engine

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

Access rights per client and object definable

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

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.