DBMS > Amazon DynamoDB vs. Google Cloud Datastore vs. Microsoft Azure SQL Database vs. Quasardb

System Properties Comparison Amazon DynamoDB vs. Google Cloud Datastore vs. Microsoft Azure SQL Database vs. Quasardb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Distributed, high-performance timeseries database

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/dynamodb

cloud.google.com/datastore

azure.microsoft.com/en-us/products/azure-sql/database

quasar.ai

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.microsoft.com/en-us/azure/azure-sql

doc.quasar.ai/master

Developer

Amazon

Google

Microsoft

quasardb

Initial release

2012

2008

2010

2009

Current release

V12

3.14.1, January 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Server operating systems

hosted

BSD
Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

integer and binary

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

with tags

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

ADO.NET
JDBC
ODBC

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

using Google App Engine

Transact SQL

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes, with always 3 replicas available

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

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

yes

via ReferenceProperties or Ancestor paths

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

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)

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.