DBMS > FoundationDB vs. IBM Cloudant vs. Kinetica vs. Microsoft Azure Cosmos DB

System Properties Comparison FoundationDB vs. IBM Cloudant vs. Kinetica vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Ordered key-value store. Core features are complimented by layers.

Database as a Service offering based on Apache CouchDB

Fully vectorized database across both GPUs and CPUs

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

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

Website

github.com/apple/foundationdb

www.ibm.com/products/cloudant

www.kinetica.com

azure.microsoft.com/services/cosmos-db

Technical documentation

apple.github.io/foundationdb

cloud.ibm.com/docs/Cloudant

docs.kinetica.com

learn.microsoft.com/azure/cosmos-db

Developer

FoundationDB

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Kinetica

Microsoft

Initial release

2013

2010

2012

2014

Current release

6.2.28, November 2020

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

C++

Erlang

C, C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

hosted

Data scheme

schema-free

some layers support schemas

schema-free

yes

schema-free

Typing

predefined data types such as float or date

some layers support typing

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

supported in specific SQL layer only

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

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

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
Java
JavaScript
Objective-C
PHP
Ruby

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

in SQL-layer only

View functions (Map-Reduce) in JavaScript

user defined functions

JavaScript

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

in SQL-layer only

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

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.

yes

GPU vRAM or System RAM

User concepts

Access control

Access rights for users can be defined per database

Access rights for users and roles on table level

Access rights can be defined down to the item level

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.