DBMS > BoltDB vs. FoundationDB vs. Google Cloud Datastore vs. RocksDB vs. Tibero

System Properties Comparison BoltDB vs. FoundationDB vs. Google Cloud Datastore vs. RocksDB vs. Tibero

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

An embedded key-value store for Go.

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

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

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store

Key-value store

Relational DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

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

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

github.com/boltdb/bolt

github.com/apple/foundationdb

cloud.google.com/datastore

rocksdb.org

us.tmaxsoft.com/products/tibero

Technical documentation

apple.github.io/foundationdb

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

FoundationDB

Google

Facebook, Inc.

TmaxSoft

Initial release

2013

2008

2013

2003

Current release

6.2.28, November 2020

9.2.1, May 2024

6, April 2015

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Open Source

BSD

commercial

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

C and Assembler

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

Linux

AIX
HP-UX
Linux
Solaris
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

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)

yes

APIs and other access methods

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

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

in SQL-layer only

using Google App Engine

Persistent Stored Procedure (PSM)

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication using Paxos

yes

Multi-source replication
Source-replica replication

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

none

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

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

planned for next version

User concepts

Access control

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.