DBMS > FoundationDB vs. Google BigQuery vs. OpenTSDB vs. PostGIS vs. TinkerGraph

System Properties Comparison FoundationDB vs. Google BigQuery vs. OpenTSDB vs. PostGIS vs. TinkerGraph

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.

Large scale data warehouse service with append-only tables

Scalable Time Series DBMS based on HBase

Spatial extension of PostgreSQL

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Secondary database models

Relational 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	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

github.com/apple/foundationdb

cloud.google.com/bigquery

opentsdb.net

postgis.net

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

apple.github.io/foundationdb

cloud.google.com/bigquery/docs

opentsdb.net/docs/build/html/index.html

postgis.net/documentation

Developer

FoundationDB

Google

currently maintained by Yahoo and other contributors

Initial release

2013

2010

2011

2005

2009

Current release

6.2.28, November 2020

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

LGPL

Open Source

GPL v2.0

Open Source

Apache 2.0

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

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

schema-free

some layers support schemas

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

some layers support typing

yes

numeric data for metrics, strings for tags

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

HTTP API
Telnet API

TinkerPop 3

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Erlang
Go
Java
Python
R
Ruby

Groovy
Java

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

based on HBase

Immediate Consistency

none

Foreign keys

Referential integrity

in SQL-layer only

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

based on PostgreSQL

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.