DBMS > FoundationDB vs. Microsoft SQL Server vs. Prometheus vs. Realm vs. ToroDB

System Properties Comparison FoundationDB vs. Microsoft SQL Server vs. Prometheus vs. Realm vs. ToroDB

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.

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

Description

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

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Document store
Graph DBMS
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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

github.com/apple/foundationdb

www.microsoft.com/en-us/sql-server

prometheus.io

realm.io

github.com/torodb/server

Technical documentation

apple.github.io/foundationdb

learn.microsoft.com/en-US/sql/sql-server

prometheus.io/docs

realm.io/docs

Developer

FoundationDB

Microsoft

Realm, acquired by MongoDB in May 2019

8Kdata

Initial release

2013

1989

2015

2014

2016

Current release

6.2.28, November 2020

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

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

Linux
Windows

Android
Backend: server-less
iOS
Windows

All OS with a Java 7 VM

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

Numeric data only

yes

string, integer, double, boolean, date, object_id

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

in SQL-layer only

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

yes

by Federation

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

Eventual 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

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

yes

Access rights for users and roles

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.