DBMS > Amazon DynamoDB vs. Datomic vs. DuckDB vs. PlanetScale

System Properties Comparison Amazon DynamoDB vs. Datomic vs. DuckDB 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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

An embeddable, in-process, column-oriented SQL OLAP RDBMS

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

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

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	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.57
Rank	#74	Overall
	#40	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

aws.amazon.com/dynamodb

www.datomic.com

duckdb.org

planetscale.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.datomic.com

duckdb.org/docs

planetscale.com/docs

Developer

Amazon

Cognitect

PlanetScale

Initial release

2012

2018

2020

Current release

1.0.6735, June 2023

0.10, February 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

limited edition free

Open Source

MIT License

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, Clojure

C++

Server operating systems

hosted

All OS with a Java VM

server-less

Docker
Linux
macOS

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
Java

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

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

yes

Transaction Functions

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

none

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

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

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

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.