DBMS > Amazon DynamoDB vs. Apache Druid vs. Citus vs. PlanetScale

System Properties Comparison Amazon DynamoDB vs. Apache Druid vs. Citus vs. PlanetScale

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/dynamodb

druid.apache.org

www.citusdata.com

planetscale.com

Technical documentation

docs.aws.amazon.com/dynamodb

druid.apache.org/docs/latest/design

docs.citusdata.com

planetscale.com/docs

Developer

Amazon

Apache Software Foundation and contributors

PlanetScale

Initial release

2012

2010

2020

Current release

29.0.1, April 2024

8.1, December 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache license v2

Open Source

AGPL, commercial license also available

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

Java

Server operating systems

hosted

Linux
OS X
Unix

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-less columns are supported

yes

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

standard, with numerous extensions

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.