DBMS > Amazon DynamoDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Qdrant

System Properties Comparison Amazon DynamoDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Qdrant

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

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

A high-performance vector database with neural network or semantic-based matching

Primary database model

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Vector DBMS

Secondary database models

Spatial DBMS

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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Website

aws.amazon.com/dynamodb

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/dynamodb

learn.microsoft.com/azure/cosmos-db

qdrant.tech/documentation

Developer

Amazon

Microsoft

Qdrant

Initial release

2012

2014

2012

2021

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

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

Rust

Server operating systems

hosted

Docker
Linux
macOS
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

Numbers, Strings, Geo, Boolean

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

All properties auto-indexed by default

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

by integration with AWS Lambda

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

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

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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 can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Key-based authentication

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.