DBMS > Amazon DynamoDB vs. Apache Phoenix vs. Cachelot.io vs. PlanetScale

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. Cachelot.io 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

A scale-out RDBMS with evolutionary schema built on Apache HBase

In-memory caching system

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

Primary database model

Document store
Key-value store

Relational DBMS

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	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

cachelot.io

planetscale.com

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

planetscale.com/docs

Developer

Amazon

Apache Software Foundation

PlanetScale

Initial release

2012

2014

2015

2020

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Simplified BSD 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

C++

Server operating systems

hosted

Linux
Unix
Windows

FreeBSD
Linux
OS X

Docker
Linux
macOS

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

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

JDBC

Memcached protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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)

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

none

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)

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.