DBMS > FoundationDB vs. Google BigQuery vs. Spark SQL vs. TinkerGraph vs. Transbase

System Properties Comparison FoundationDB vs. Google BigQuery vs. Spark SQL vs. TinkerGraph vs. Transbase

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Graph 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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

github.com/apple/foundationdb

cloud.google.com/bigquery

spark.apache.org/sql

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

www.transaction.de/en/products/transbase.html

Technical documentation

apple.github.io/foundationdb

cloud.google.com/bigquery/docs

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

FoundationDB

Google

Apache Software Foundation

Transaction Software GmbH

Initial release

2013

2010

2014

2009

1987

Current release

6.2.28, November 2020

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

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

Scala

Java

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

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

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.

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

TinkerPop 3

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Python
R
Scala

Groovy
Java

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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

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.