DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon DynamoDB vs. Microsoft Access vs. Percona Server for MySQL vs. Tarantool

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. Amazon DynamoDB vs. Microsoft Access vs. Percona Server for MySQL vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

An online MPP (Massively Parallel Processing) data warehousing service based on Greenplum

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.68
Rank	#231	Overall
	#105	Relational DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.alibabacloud.com/product/hybriddb-postgresql

aws.amazon.com/dynamodb

www.microsoft.com/en-us/microsoft-365/access

www.percona.com/software/mysql-database/percona-server

www.tarantool.io

Technical documentation

www.alibabacloud.com/help/en/analyticdb-for-postgresql/latest/product-introduction-overview

docs.aws.amazon.com/dynamodb

developer.microsoft.com/en-us/access

www.percona.com/downloads/Percona-Server-LATEST

www.tarantool.io/en/doc

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Amazon

Microsoft

Percona

Initial release

2016

2012

1992

2008

Current release

1902 (16.0.11328.20222), March 2019

8.0.36-28, 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Bundled with Microsoft Office

Open Source

GPL version 2

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C++

C and C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux

BSD
Linux
macOS

Data scheme

yes

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

but not compliant to any SQL standard

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC

Open binary protocol

Supported programming languages

C
Java
Perl
Python
R

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes

since Access 2010 using the ACE-engine

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

none

Multi-source replication
Source-replica replication
XtraDB Cluster

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

but no files for transaction logging

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

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)

a simple user-level security was built in till version Access 2003

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.