DBMS > MariaDB vs. Microsoft Access vs. Oracle Berkeley DB vs. YugabyteDB

System Properties Comparison MariaDB vs. Microsoft Access vs. Oracle Berkeley DB vs. YugabyteDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used in-process key-value store

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Document store
Wide column store

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

Score	91.04
Rank	#13	Overall
	#9	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	2.63
Rank	#109	Overall
	#53	Relational DBMS

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

www.oracle.com/database/technologies/related/berkeleydb.html

www.yugabyte.com

Technical documentation

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

docs.oracle.com/cd/E17076_05/html/index.html

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

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

The lead developer Monty Widenius is the original author of MySQL

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Yugabyte Inc.

Initial release

2009

Fork of MySQL, which was first released in 1995

1992

1994

2017

Current release

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

18.1.40, May 2020

2.19, September 2023

License

Commercial or Open Source

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

Open Source

commercial license available

Open Source

Apache 2.0

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.

STACKIT MariaDB offers MariaDB in a fully managed version in enterprise grade, 100% GDPR-compliant.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

C and C++

C++

C, Java, C++ (depending on the Berkeley DB edition)

C and C++

Server operating systems

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Data scheme

yes

Dynamic columns are supported

yes

schema-free

depending on used data model

Typing

predefined data types such as float or date

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

but not compliant to any SQL standard

yes

SQL interfaced based on SQLite is available

yes, PostgreSQL compatible

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

yes

sql, plpgsql, C

Triggers

yes

since Access 2010 using the ACE-engine

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

several options for horizontal partitioning and Sharding

none

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

but no files for transaction logging

ACID

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

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

yes

based on RocksDB

In-memory capabilities

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

yes

with MEMORY storage engine

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

yes

More information provided by the system vendor

Specific characteristics

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

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

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

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

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

Systems of record and engagement for cloud native applications that require resilience,...
» 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

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

Apache 2.0 license for the database
» 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.