DBMS > GBase vs. GridDB vs. Ignite vs. MariaDB vs. Microsoft Access

System Properties Comparison GBase vs. GridDB vs. Ignite vs. MariaDB vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Scalable in-memory time series database optimized for IoT and Big Data

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

Relational DBMS

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

Technical documentation

docs.griddb.net

apacheignite.readme.io/docs

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

Developer

General Data Technology Co., Ltd.

Toshiba Corporation

Apache Software Foundation

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

The lead developer Monty Widenius is the original author of MySQL

Microsoft

Initial release

2004

2013

2015

2009

Fork of MySQL, which was first released in 1995

1992

Current release

GBase 8a, GBase 8s, GBase 8c

5.1, August 2022

Apache Ignite 2.6

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache 2.0

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.

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

Implementation language

C, Java, Python

C++

C++, Java, .Net

C and C++

C++

Server operating systems

Linux

Linux
OS X
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

yes

Dynamic columns are supported

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

Standard with numerous extensions

SQL92, SQL-like TQL (Toshiba Query Language)

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

but not compliant to any SQL standard

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
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

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

Triggers

yes

yes (cache interceptors and events)

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

several options for horizontal partitioning and Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes (replicated cache)

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

ACID

ACID at container level

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

yes

Access rights for users can be defined per database

Security Hooks for custom implementations

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

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

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

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

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

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

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

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

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

Market metrics

GitHub trending repository
» more

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

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.