DBMS > Atos Standard Common Repository vs. Cloudflare Workers KV vs. Microsoft Access vs. Snowflake vs. YDB

System Properties Comparison Atos Standard Common Repository vs. Cloudflare Workers KV vs. Microsoft Access vs. Snowflake vs. YDB

Editorial information provided by DB-Engines

Name

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

Description

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

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

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

Cloud-based data warehousing service for structured and semi-structured data

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Document store
Relational DBMS

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

Score	0.39
Rank	#278	Overall
	#39	Key-value stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.34
Rank	#285	Overall
	#43	Document stores
	#130	Relational DBMS

Website

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

www.cloudflare.com/developer-platform/workers-kv

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

www.snowflake.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

developers.cloudflare.com/kv/api

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

ydb.tech/en/docs

Developer

Atos Convergence Creators

Cloudflare

Microsoft

Snowflake Computing Inc.

Yandex

Initial release

2016

2018

1992

2014

2019

Current release

1703

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache 2.0; commercial license 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++

Server operating systems

Linux

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

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

yes

but not compliant to any SQL standard

yes

SQL-like query language (YQL)

APIs and other access methods

LDAP

HTTP REST
Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

All languages with LDAP bindings

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

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

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

but no files for transaction logging

ACID

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

LDAP bind authentication

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights defined for Yandex Cloud users

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.