DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. GBase vs. Microsoft Access vs. Yanza

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. GBase vs. Microsoft Access vs. Yanza

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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.)

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

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

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/dynamodb

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.gbase.cn

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

yanza.com

Technical documentation

docs.aws.amazon.com/dynamodb

developer.microsoft.com/en-us/access

Developer

Amazon

Atos Convergence Creators

General Data Technology Co., Ltd.

Microsoft

Yanza

Initial release

2012

2016

2004

1992

2015

Current release

1703

GBase 8a, GBase 8s, GBase 8c

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Bundled with Microsoft Office

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C, Java, Python

C++

Server operating systems

hosted

Linux

Windows

Not a real database server, but making use of DLLs

Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Standard with numerous extensions

yes

but not compliant to any SQL standard

APIs and other access methods

RESTful HTTP API

LDAP

ADO.NET
C API
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

Triggers

yes

by integration with AWS Lambda

yes

since Access 2010 using the ACE-engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning (by range, list and hash) and vertical partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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 or Eventual Consistency depending on configuration

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

Atomic execution of specific operations

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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)

LDAP bind authentication

yes

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

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.