DBMS > Amazon DynamoDB vs. FoundationDB vs. Google Cloud Bigtable vs. Tarantool vs. Trino

System Properties Comparison Amazon DynamoDB vs. FoundationDB vs. Google Cloud Bigtable vs. Tarantool vs. Trino

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Document store
Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.97
Rank	#191	Overall
	#32	Document stores
	#28	Key-value stores
	#87	Relational DBMS

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	1.63
Rank	#139	Overall
	#25	Document stores
	#24	Key-value stores
	#65	Relational DBMS

Score	5.28
Rank	#61	Overall
	#35	Relational DBMS

Website

aws.amazon.com/dynamodb

github.com/apple/foundationdb

cloud.google.com/bigtable

www.tarantool.io

trino.io

Technical documentation

docs.aws.amazon.com/dynamodb

apple.github.io/foundationdb

cloud.google.com/bigtable/docs

www.tarantool.io/en/doc

trino.io/broadcast
trino.io/docs/current

Developer

Amazon

FoundationDB

Google

Trino Software Foundation

Initial release

2012

2013

2015

2008

2012

2020 rebranded from PrestoSQL

Current release

6.2.28, November 2020

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache Version 2.0

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

Java

Server operating systems

hosted

Linux
OS X
Windows

hosted

BSD
Linux
macOS

Linux
macOS

for devlopment

Data scheme

schema-free

some layers support schemas

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

some layers support typing

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Secondary indexes

yes

depending on connected data-source

SQL

Support of SQL

supported in specific SQL layer only

Full-featured ANSI SQL support

yes

APIs and other access methods

RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Open binary protocol

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

Lua, C and SQL stored procedures

yes, depending on connected data-source

Triggers

yes

by integration with AWS Lambda

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

depending on connected data-source

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Linearizable consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

depending on connected data-source

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Atomic single-row operations

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

depending on connected data-source

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

depending on connected data-source

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

SQL standard access control

More information provided by the system vendor

News

23 is a go, keeping pace with Java
17 September 2024

65: Performance boosts
12 September 2024

64: Control with Open Policy Agent OPA
22 August 2024

63: Querying with JS
1 August 2024

62: A lakehouse that simply works at Prezi
11 July 2024

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.