DBMS > Citus vs. FatDB vs. RethinkDB vs. RocksDB

System Properties Comparison Citus vs. FatDB vs. RethinkDB vs. RocksDB

Please select another system to include it in the comparison.

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Key-value store

Secondary database models

Document store

Spatial DBMS

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.citusdata.com

rethinkdb.com

rocksdb.org

Technical documentation

docs.citusdata.com

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

Developer

FatCloud

The Linux Foundation

since July 2017

Facebook, Inc.

Initial release

2010

2012

2009

2013

Current release

8.1, December 2018

2.4.1, August 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache Version 2

Open Source

BSD

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++

Server operating systems

Linux

Windows

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

Via inetgration in SQL Server

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

via applications

Triggers

yes

via applications

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-document operations

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

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

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

yes

users and table-level permissions

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.