DBMS > Amazon Aurora vs. Amazon DynamoDB vs. Apache Phoenix vs. HEAVY.AI

System Properties Comparison Amazon Aurora vs. Amazon DynamoDB vs. Apache Phoenix vs. HEAVY.AI

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Relational DBMS

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	7.84
Rank	#44	Overall
	#28	Relational DBMS

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Website

aws.amazon.com/rds/aurora

aws.amazon.com/dynamodb

phoenix.apache.org

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/dynamodb

phoenix.apache.org

docs.heavy.ai

Developer

Amazon

Apache Software Foundation

HEAVY.AI, Inc.

Initial release

2015

2012

2014

2016

Current release

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

5.10, January 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

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++ and CUDA

Server operating systems

hosted

Linux
Unix
Windows

Linux

Data scheme

yes

schema-free

yes

late-bound, schema-on-read capabilities

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

JDBC

JDBC
ODBC
Thrift
Vega

Supported programming languages

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

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

Multi-source 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

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

fine grained access rights according to SQL-standard

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

fine grained access rights according to SQL-standard

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.