DBMS > Amazon DynamoDB vs. Apache Druid vs. Google Cloud Datastore vs. SwayDB

System Properties Comparison Amazon DynamoDB vs. Apache Druid vs. Google Cloud Datastore vs. SwayDB

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Document store

Key-value store

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.04
Rank	#373	Overall
	#57	Key-value stores

Website

aws.amazon.com/dynamodb

druid.apache.org

cloud.google.com/datastore

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/dynamodb

druid.apache.org/docs/latest/design

cloud.google.com/datastore/docs

Developer

Amazon

Apache Software Foundation and contributors

Google

Simer Plaha

Initial release

2012

2008

2018

Current release

29.0.1, April 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache license v2

commercial

Open Source

GNU Affero GPL V3.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

Java

Scala

Server operating systems

hosted

Linux
OS X
Unix

hosted

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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 for querying

SQL-like query language (GQL)

APIs and other access methods

RESTful HTTP API

JDBC
RESTful HTTP/JSON API

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

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

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

Atomic execution of operations

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)

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.