DBMS > FoundationDB vs. Oracle NoSQL vs. Snowflake vs. TerarkDB

System Properties Comparison FoundationDB vs. Oracle NoSQL vs. Snowflake vs. TerarkDB

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.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store
Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Score	0.97
Rank	#191	Overall
	#32	Document stores
	#28	Key-value stores
	#87	Relational DBMS

Score	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

github.com/apple/foundationdb

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

apple.github.io/foundationdb

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

FoundationDB

Oracle

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2013

2011

2014

2016

Current release

6.2.28, November 2020

24.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

restricted open source version 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

C++

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
Solaris SPARC/x86

hosted

Data scheme

schema-free

some layers support schemas

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

schema-free

Typing

predefined data types such as float or date

some layers support typing

optional

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

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

ACID

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

off heap cache

yes

User concepts

Access control

Access rights for users and roles

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.