DBMS > CouchDB vs. FatDB vs. Geode vs. RocksDB

System Properties Comparison CouchDB vs. FatDB vs. Geode 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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

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

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

Primary database model

Document store

Document store
Key-value store

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Website

couchdb.apache.org

geode.apache.org

rocksdb.org

Technical documentation

docs.couchdb.org/en/stable

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

FatCloud

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Facebook, Inc.

Initial release

2005

2012

2002

2013

Current release

3.3.3, December 2023

1.1, February 2017

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Erlang

Java

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (OQL)

APIs and other access methods

RESTful HTTP/JSON API

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

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

yes, on a single node

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

Can implement custom security layer via applications

Access rights per client and object definable

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.