DBMS > FatDB vs. Greenplum vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RavenDB

System Properties Comparison FatDB vs. Greenplum vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RavenDB

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 .NET NoSQL DBMS that can integrate with and extend SQL Server.

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

greenplum.org

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

ravendb.net

Technical documentation

docs.greenplum.org

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

Developer

FatCloud

Pivotal Software Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Hibernating Rhinos

Initial release

2012

2005

2010

2014

2010

Current release

7.0.0, September 2023

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

AGPL version 3, commercial license available

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

Erlang

Server operating systems

Windows

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

since Version 4.2

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

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

JDBC
ODBC

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C
Java
Perl
Python
R

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

yes

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes

via applications

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

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.

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.