DBMS > Atos Standard Common Repository vs. BaseX vs. GigaSpaces vs. MariaDB vs. Microsoft Access

System Properties Comparison Atos Standard Common Repository vs. BaseX vs. GigaSpaces vs. MariaDB vs. Microsoft Access

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

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

Primary database model

Document store
Key-value store

Native XML DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Secondary database models

Graph DBMS
Search engine

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

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

basex.org

www.gigaspaces.com

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

Technical documentation

docs.basex.org

docs.gigaspaces.com/latest/landing.html

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

Developer

Atos Convergence Creators

BaseX GmbH

Gigaspaces Technologies

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Microsoft

Initial release

2016

2007

2000

2009

Fork of MySQL, which was first released in 1995

1992

Current release

1703

10.7, August 2023

15.5, September 2020

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache Version 2; Commercial licenses available

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

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.

Implementation language

Java

Java, C++, .Net

C and C++

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Solaris
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Dynamic columns are supported

yes

Typing

predefined data types such as float or date

optional

XQuery supports types

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

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

with proprietary extensions

yes

but not compliant to any SQL standard

APIs and other access methods

LDAP

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
C++
Java
Python
Scala

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

Triggers

yes

via events

yes, event driven architecture

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

several options for horizontal partitioning and Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of specific operations

multiple readers, single writer

ACID

not for MyISAM storage engine

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

but no files for transaction logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

with MEMORY storage engine

User concepts

Access control

LDAP bind authentication

Users with fine-grained authorization concept on 4 levels

Role-based access control

fine grained access rights according to SQL-standard

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

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» 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.