DBMS > Dolt vs. Geode vs. MySQL vs. Riak KV vs. RRDtool

System Properties Comparison Dolt vs. Geode vs. MySQL vs. Riak KV vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Widely used open source RDBMS

Distributed, fault tolerant key-value store

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

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

geode.apache.org

www.mysql.com

oss.oetiker.ch/rrdtool

Technical documentation

docs.dolthub.com

geode.apache.org/docs

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/kv/latest

oss.oetiker.ch/rrdtool/doc

Developer

DoltHub Inc

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

OpenSource, formerly Basho Technologies

Tobias Oetiker

Initial release

2018

2002

1995

2009

1999

Current release

1.1, February 2017

8.4.0, April 2024

3.2.0, December 2022

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache version 2, commercial enterprise edition

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

Java

C and C++

Erlang

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

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

HP-UX
Linux

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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

restricted

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

with proprietary extensions

APIs and other access methods

CLI Client
HTTP REST

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

in-process shared library
Pipes

Supported programming languages

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

.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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

currently in alpha release

user defined functions

yes

proprietary syntax

Erlang

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

Multi-source replication
Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between data sets can be stored

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

by using the rrdcached daemon

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

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Access rights per client and object definable

Users with fine-grained authorization concept

no user groups or roles

yes, using Riak Security

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.