DBMS > FoundationDB vs. MariaDB vs. Microsoft Access vs. ScyllaDB

System Properties Comparison FoundationDB vs. MariaDB vs. Microsoft Access vs. ScyllaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Ordered key-value store. Core features are complimented by layers.

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

Cassandra and DynamoDB compatible wide column store

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Wide column store

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Key-value store

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

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Website

github.com/apple/foundationdb

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

www.scylladb.com

Technical documentation

apple.github.io/foundationdb

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

docs.scylladb.com

Developer

FoundationDB

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

The lead developer Monty Widenius is the original author of MySQL

Microsoft

ScyllaDB

Initial release

2013

2009

Fork of MySQL, which was first released in 1995

1992

2015

Current release

6.2.28, November 2020

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

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.

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

Implementation language

C++

C and C++

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

schema-free

some layers support schemas

yes

Dynamic columns are supported

yes

schema-free

Typing

predefined data types such as float or date

some layers support typing

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

supported in specific SQL layer only

yes

with proprietary extensions

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements (CQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Proprietary protocol (CQL)

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

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

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

in SQL-layer only

yes

PL/SQL compatibility added with version 10.3

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

several options for horizontal partitioning and Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

Linearizable consistency

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

in SQL-layer only

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

Atomicity and isolation are supported for single operations

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

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

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

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

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

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

Competitive advantages

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

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

Typical application scenarios

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

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

Key customers

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

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

Market metrics

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

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

Licensing and pricing models

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

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.