DBMS > Atos Standard Common Repository vs. ClickHouse vs. Microsoft Access vs. RocksDB vs. ScyllaDB

System Properties Comparison Atos Standard Common Repository vs. ClickHouse vs. Microsoft Access vs. RocksDB vs. ScyllaDB

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 high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Cassandra and DynamoDB compatible wide column store

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Wide column store

Secondary database models

Time Series DBMS

Key-value store

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	4.08
Rank	#76	Overall
	#5	Wide column stores

Website

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

clickhouse.com

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

rocksdb.org

www.scylladb.com

Technical documentation

clickhouse.com/docs

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

docs.scylladb.com

Developer

Atos Convergence Creators

Clickhouse Inc.

Microsoft

Facebook, Inc.

ScyllaDB

Initial release

2016

1992

2013

2015

Current release

1703

v24.4.2.141-stable, June 2024

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

Open Source (AGPL), commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

Java

C++

Server operating systems

Linux

FreeBSD
Linux
macOS

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

Schema and schema-less with LDAP views

yes

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

cluster global secondary indices

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements (CQL)

APIs and other access methods

LDAP

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Supported programming languages

All languages with LDAP bindings

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

C
C++
Go
Java
Perl
Python
Ruby

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes, Lua

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

key based and custom

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

none

yes

selectable replication factor

Representation of geographical distribution of servers is possible

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

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

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

yes

Atomicity and isolation are supported for single operations

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

in-memory tables

User concepts

Access control

LDAP bind authentication

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.