DBMS > FoundationDB vs. Graphite vs. OrigoDB vs. Snowflake

System Properties Comparison FoundationDB vs. Graphite vs. OrigoDB 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.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A fully ACID in-memory object graph database

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

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

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

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/apple/foundationdb

github.com/graphite-project/graphite-web

origodb.com

www.snowflake.com

Technical documentation

apple.github.io/foundationdb

graphite.readthedocs.io

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

FoundationDB

Chris Davis

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2013

2006

2009

under the name LiveDB

2014

Current release

6.2.28, November 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

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++

Python

Server operating systems

Linux
OS X
Windows

Linux
Unix

Linux
Windows

hosted

Data scheme

schema-free

some layers support schemas

yes

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

Typing

predefined data types such as float or date

some layers support typing

Numeric data only

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

HTTP API
Sockets

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

JavaScript (Node.js)
Python

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in SQL-layer only

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

none

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.