DBMS > FoundationDB vs. IBM Cloudant vs. Netezza vs. Snowflake

System Properties Comparison FoundationDB vs. IBM Cloudant vs. Netezza vs. Snowflake

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

Data warehouse and analytics appliance part of IBM PureSystems

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store

Relational DBMS

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

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/apple/foundationdb

www.ibm.com/products/cloudant

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

apple.github.io/foundationdb

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

FoundationDB

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Snowflake Computing Inc.

Initial release

2013

2010

2000

2014

Current release

6.2.28, November 2020

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

Server operating systems

Linux
OS X
Windows

hosted

Linux

included in appliance

hosted

Data scheme

schema-free

some layers support schemas

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

some layers support typing

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.

yes

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in SQL-layer only

View functions (Map-Reduce) in JavaScript

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Linearizable consistency

Eventual Consistency

Immediate 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

ACID

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

Access rights for users can be defined per database

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

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.