DBMS > Atos Standard Common Repository vs. Derby vs. Microsoft Access vs. Snowflake vs. WakandaDB

System Properties Comparison Atos Standard Common Repository vs. Derby vs. Microsoft Access vs. Snowflake vs. WakandaDB

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Key-value store

Relational DBMS

Object oriented DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

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

db.apache.org/derby

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

www.snowflake.com

wakanda.github.io

Technical documentation

db.apache.org/derby/manuals/index.html

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

Atos Convergence Creators

Apache Software Foundation

Microsoft

Snowflake Computing Inc.

Wakanda SAS

Initial release

2016

1997

1992

2014

2012

Current release

1703

10.17.1.0, November 2023

1902 (16.0.11328.20222), March 2019

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPLv3, extended 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++

C++, JavaScript

Server operating systems

Linux

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

yes

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

yes

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

APIs and other access methods

LDAP

JDBC

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

Java

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

JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

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

fine grained access rights according to SQL-standard

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

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

yes

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.