DBMS > FoundationDB vs. Google BigQuery vs. Oracle Rdb vs. Solr

System Properties Comparison FoundationDB vs. Google BigQuery vs. Oracle Rdb vs. Solr

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.

Large scale data warehouse service with append-only tables

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Search engine

Secondary database models

Spatial 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	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

github.com/apple/foundationdb

cloud.google.com/bigquery

www.oracle.com/database/technologies/related/rdb.html

solr.apache.org

Technical documentation

apple.github.io/foundationdb

cloud.google.com/bigquery/docs

www.oracle.com/database/technologies/related/rdb-doc.html

solr.apache.org/resources.html

Developer

FoundationDB

Google

Oracle, originally developed by Digital Equipment Corporation (DEC)

Apache Software Foundation

Initial release

2013

2010

1984

2006

Current release

6.2.28, November 2020

7.4.1.1, 2021

9.6.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2

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

HP Open VMS

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

some layers support schemas

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

some layers support typing

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

supported in specific SQL layer only

yes

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

in JavaScript

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

Eventual 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

yes, on a single node

optimistic locking

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

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.