DBMS > Citus vs. FatDB vs. IRONdb vs. RocksDB

System Properties Comparison Citus vs. FatDB vs. IRONdb 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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines 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.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

Key-value store

Secondary database models

Document store

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

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

Website

www.citusdata.com

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

docs.citusdata.com

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

FatCloud

Circonus LLC.

Facebook, Inc.

Initial release

2010

2012

2017

2013

Current release

8.1, December 2018

V0.10.20, January 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

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

C++

Server operating systems

Linux

Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

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

HTTP API

C++ API
Java API

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

yes, in Lua

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

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

configurable replication factor, datacenter aware

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 per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

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.