DBMS > Microsoft Access vs. MySQL vs. Tarantool vs. VoltDB

System Properties Comparison Microsoft Access vs. MySQL vs. Tarantool vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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 open source RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

www.mysql.com

www.tarantool.io

www.voltdb.com

Technical documentation

developer.microsoft.com/en-us/access

dev.mysql.com/doc

www.tarantool.io/en/doc

docs.voltdb.com

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

VoltDB Inc.

Initial release

1992

1995

2008

2010

Current release

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

2.10.0, May 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Java, C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Linux
OS X

for development

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with proprietary extensions

Full-featured ANSI SQL support

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Lua, C and SQL stored procedures

Java

Triggers

yes

since Access 2010 using the ACE-engine

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, cooperative multitasking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

yes, write ahead logging

yes

Snapshots and command logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

Users and roles with access to stored procedures

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.