DBMS > FoundationDB vs. Google Cloud Datastore vs. jBASE vs. Microsoft SQL Server

System Properties Comparison FoundationDB vs. Google Cloud Datastore vs. jBASE vs. Microsoft SQL Server

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A robust multi-value DBMS comprising development tools and middleware

Microsofts flagship relational DBMS

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/apple/foundationdb

cloud.google.com/datastore

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

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

Technical documentation

apple.github.io/foundationdb

cloud.google.com/datastore/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

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

Developer

FoundationDB

Google

Rocket Software (formerly Zumasys)

Microsoft

Initial release

2013

2008

1991

1989

Current release

6.2.28, November 2020

5.7

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

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

hosted

AIX
Linux
Windows

Linux
Windows

Data scheme

schema-free

some layers support schemas

schema-free

yes

Typing

predefined data types such as float or date

some layers support typing

yes, details here

optional

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

SQL-like query language (GQL)

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

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

Server-side scripts

Stored procedures

in SQL-layer only

using Google App Engine

yes

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

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights can be defined down to the item level

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.