DBMS > Amazon DynamoDB vs. Apache Impala vs. Fauna vs. Google Cloud Bigtable vs. Tarantool

System Properties Comparison Amazon DynamoDB vs. Apache Impala vs. Fauna vs. Google Cloud Bigtable vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for Hadoop

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

Spatial DBMS

with Tarantool/GIS extension

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	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.55
Rank	#151	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

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

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

aws.amazon.com/dynamodb

impala.apache.org

fauna.com

cloud.google.com/bigtable

www.tarantool.io

Technical documentation

docs.aws.amazon.com/dynamodb

impala.apache.org/impala-docs.html

docs.fauna.com

cloud.google.com/bigtable/docs

www.tarantool.io/en/doc

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Fauna, Inc.

Google

Initial release

2012

2013

2014

2015

2008

Current release

4.1.0, June 2022

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Open Source

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

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

Scala

C and C++

Server operating systems

hosted

Linux

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

schema-free

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

Typing

predefined data types such as float or date

yes

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

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

SQL

Support of SQL

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

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

Open binary protocol

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

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

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

Lua, C and SQL stored procedures

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

horizontal partitioning

consistent hashing

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

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)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate 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

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

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 Apache Sentry and Kerberos

Identity management, authentication, and access control

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

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.