DBMS > Amazon DynamoDB vs. FoundationDB vs. Google Cloud Bigtable vs. GridGain vs. TerarkDB

System Properties Comparison Amazon DynamoDB vs. FoundationDB vs. Google Cloud Bigtable vs. GridGain vs. TerarkDB

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.

GridGain is an in-memory computing platform, built on Apache Ignite

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Key-value store
Relational DBMS

Key-value store

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

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

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

aws.amazon.com/dynamodb

github.com/apple/foundationdb

cloud.google.com/bigtable

www.gridgain.com

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/dynamodb

apple.github.io/foundationdb

cloud.google.com/bigtable/docs

www.gridgain.com/docs/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon

FoundationDB

Google

GridGain Systems, Inc.

ByteDance, originally Terark

Initial release

2012

2013

2015

2007

2016

Current release

6.2.28, November 2020

GridGain 8.5.1

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

commercial

restricted open source version 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++

Java, C++, .Net

C++

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

some layers support schemas

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

RESTful HTTP API

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

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++
Java
PHP
Python
Ruby
Scala

C++
Java

Server-side scripts

Stored procedures

in SQL-layer only

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

by integration with AWS Lambda

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

yes (compute grid and hadoop accelerator)

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)

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

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

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

Security Hooks for custom implementations

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.