DBMS > Fauna vs. OrigoDB vs. RocksDB vs. RRDtool

System Properties Comparison Fauna vs. OrigoDB vs. RocksDB vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

A fully ACID in-memory object graph database

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

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Document store
Object oriented DBMS

Key-value store

Time Series DBMS

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

Score	1.55
Rank	#151	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

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

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

fauna.com

origodb.com

rocksdb.org

oss.oetiker.ch/rrdtool

Technical documentation

docs.fauna.com

origodb.com/docs

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

Fauna, Inc.

Robert Friberg et al

Facebook, Inc.

Tobias Oetiker

Initial release

2014

2009

under the name LiveDB

2013

1999

Current release

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

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

Server operating systems

hosted

Linux
Windows

Linux

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

can be achieved using .NET

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

.Net

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

user defined functions

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

consistent hashing

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

yes

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.

yes

User concepts

Access control

Identity management, authentication, and access control

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.