DBMS > FoundationDB vs. Google Cloud Datastore vs. Snowflake vs. SpaceTime vs. XTDB

System Properties Comparison FoundationDB vs. Google Cloud Datastore vs. Snowflake vs. SpaceTime vs. XTDB

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

Cloud-based data warehousing service for structured and semi-structured data

SpaceTime is a spatio-temporal DBMS with a focus on performance.

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Secondary database models

Relational 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	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/apple/foundationdb

cloud.google.com/datastore

www.snowflake.com

www.mireo.com/spacetime

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

apple.github.io/foundationdb

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

FoundationDB

Google

Snowflake Computing Inc.

Mireo

Juxt Ltd.

Initial release

2013

2008

2014

2020

2019

Current release

6.2.28, November 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

Clojure

Server operating systems

Linux
OS X
Windows

hosted

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

some layers support schemas

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

Typing

predefined data types such as float or date

some layers support typing

yes, details here

yes

yes, extensible-data-notation format

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)

yes

A subset of ANSI SQL is implemented

limited SQL, making use of Apache Calcite

APIs and other access methods

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

CLI Client
JDBC
ODBC

RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

JavaScript (Node.js)
Python

C#
C++
Python

Clojure
Java

Server-side scripts

Stored procedures

in SQL-layer only

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

Real-time block device replication (DRBD)

yes, each node contains all data

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.