DBMS > Amazon DynamoDB vs. Apache Impala vs. PlanetScale vs. SAP HANA vs. Valentina Server

System Properties Comparison Amazon DynamoDB vs. Apache Impala vs. PlanetScale vs. SAP HANA vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for Hadoop

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

In-memory, column based data store. Available as appliance or cloud service

Object-relational database and reports server

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

aws.amazon.com/dynamodb

impala.apache.org

planetscale.com

www.sap.com/products/hana.html

www.valentina-db.net

Technical documentation

docs.aws.amazon.com/dynamodb

impala.apache.org/impala-docs.html

planetscale.com/docs

help.sap.com/hana

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

PlanetScale

SAP

Paradigma Software

Initial release

2012

2013

2020

2010

1999

Current release

4.1.0, June 2022

2.0 SPS07 (April 4, 2023), April 2023

5.7.5

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

Linux

Docker
Linux
macOS

Appliance or cloud-service

Linux
OS X
Windows

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

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

SQLScript, R

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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 at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept

no user groups or roles

yes

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.