DBMS > FoundationDB vs. Google BigQuery vs. IRONdb vs. Postgres-XL

System Properties Comparison FoundationDB vs. Google BigQuery vs. IRONdb vs. Postgres-XL

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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Large scale data warehouse service with append-only tables

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

github.com/apple/foundationdb

cloud.google.com/bigquery

www.circonus.com/solutions/time-series-database/

www.postgres-xl.org

Technical documentation

apple.github.io/foundationdb

cloud.google.com/bigquery/docs

docs.circonus.com/irondb/category/getting-started

www.postgres-xl.org/documentation

Developer

FoundationDB

Google

Circonus LLC.

Initial release

2013

2010

2017

2014

since 2012, originally named StormDB

Current release

6.2.28, November 2020

V0.10.20, January 2018

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Mozilla public license

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

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux
macOS

Data scheme

schema-free

some layers support schemas

yes

schema-free

yes

Typing

predefined data types such as float or date

some layers support typing

yes

text, numeric, histograms

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

in JavaScript

yes, in Lua

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

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

Since BigQuery is designed for querying data

ACID

MVCC

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.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.