DBMS > BoltDB vs. FatDB vs. Percona Server for MongoDB vs. RocksDB vs. RRDtool

System Properties Comparison BoltDB vs. FatDB vs. Percona Server for MongoDB vs. RocksDB vs. RRDtool

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

An embedded key-value store for Go.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Key-value store

Document store
Key-value store

Document store

Key-value store

Time Series DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

github.com/boltdb/bolt

www.percona.com/mongodb/software/percona-server-for-mongodb

rocksdb.org

oss.oetiker.ch/rrdtool

Technical documentation

docs.percona.com/percona-distribution-for-mongodb

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

FatCloud

Percona

Facebook, Inc.

Tobias Oetiker

Initial release

2013

2012

2015

2013

1999

Current release

3.4.10-2.10, November 2017

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPL Version 2

Open Source

BSD

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

C++

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Windows

Linux

HP-UX
Linux

Data scheme

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

proprietary protocol using JSON

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
Perl
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

yes

via applications

JavaScript

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

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

via In-Memory Engine

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights for users and roles

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.