DBMS > 4D vs. Atos Standard Common Repository vs. Microsoft Access vs. RocksDB vs. Yanza

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Microsoft Access vs. RocksDB 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

Application development environment with integrated database management system

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

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)

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Time Series DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.4d.com

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

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

rocksdb.org

yanza.com

Technical documentation

developer.4d.com

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

Atos Convergence Creators

Microsoft

Facebook, Inc.

Yanza

Initial release

1984

2016

1992

2013

2015

Current release

v20, April 2023

1703

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud service

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++

Server operating systems

OS X
Windows

Linux

Windows

Not a real database server, but making use of DLLs

Linux

Windows

Data scheme

yes

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

yes

close to SQL 92

yes

but not compliant to any SQL standard

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

HTTP API

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

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

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Atomic execution of specific operations

ACID

but no files for transaction logging

yes

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

Users and groups

LDAP bind authentication

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.