DBMS > FoundationDB vs. Infobright vs. Microsoft Azure SQL Database vs. PostGIS vs. RocksDB

System Properties Comparison FoundationDB vs. Infobright vs. Microsoft Azure SQL Database vs. PostGIS vs. RocksDB

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Database as a Service offering with high compatibility to Microsoft SQL Server

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Spatial DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial 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	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

github.com/apple/foundationdb

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/en-us/products/azure-sql/database

postgis.net

rocksdb.org

Technical documentation

apple.github.io/foundationdb

docs.microsoft.com/en-us/azure/azure-sql

postgis.net/documentation

github.com/facebook/rocksdb/wiki

Developer

FoundationDB

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Facebook, Inc.

Initial release

2013

2005

2010

2005

2013

Current release

6.2.28, November 2020

V12

3.4.2, February 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Open Source

GPL v2.0

Open Source

BSD

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

Server operating systems

Linux
OS X
Windows

Linux
Windows

hosted

Linux

Data scheme

schema-free

some layers support schemas

yes

schema-free

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.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

Transact SQL

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

based on PostgreSQL

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes, with always 3 replicas available

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

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

yes

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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.