DBMS > Amazon DocumentDB vs. Amazon DynamoDB vs. EsgynDB vs. Google Cloud Firestore

System Properties Comparison Amazon DocumentDB vs. Amazon DynamoDB vs. EsgynDB vs. Google Cloud Firestore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Primary database model

Document store

Document store
Key-value store

Relational DBMS

Document store

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Website

aws.amazon.com/documentdb

aws.amazon.com/dynamodb

www.esgyn.cn

firebase.google.com/products/firestore

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/dynamodb

firebase.google.com/docs/firestore

Developer

Amazon

Esgyn

Google

Initial release

2019

2012

2015

2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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

Server operating systems

hosted

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP API

ADO.NET
JDBC
ODBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes

by integration with AWS Lambda

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication between multi datacenters

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

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

ACID

yes

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.

User concepts

Access control

Access rights for users and roles

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.