DBMS > AllegroGraph vs. MariaDB vs. Microsoft Access vs. Sqrrl vs. VoltDB

System Properties Comparison AllegroGraph vs. MariaDB vs. Microsoft Access vs. Sqrrl vs. VoltDB

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

High performance, persistent RDF store with additional support for Graph DBMS

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

Adaptable, secure NoSQL built on Apache Accumulo

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

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial 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.13
Rank	#179	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#8	Vector DBMS

Score	91.04
Rank	#13	Overall
	#9	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

allegrograph.com

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

sqrrl.com

www.voltdb.com

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

docs.voltdb.com

Developer

Franz Inc.

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

The lead developer Monty Widenius is the original author of MySQL

Microsoft

Amazon

originally Sqrrl Data, Inc.

VoltDB Inc.

Initial release

2004

2009

Fork of MySQL, which was first released in 1995

1992

2012

2010

Current release

8.0, December 2023

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

11.3, April 2022

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

commercial

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.

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

Implementation language

C and C++

C++

Java

Java, 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

Linux
OS X

for development

Data scheme

yes

RDF schemas

yes

Dynamic columns are supported

yes

schema-free

yes

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.

bulk load of XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

yes

but not compliant to any SQL standard

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API
SPARQL

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Clojure
Java
Lisp
Perl
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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

Java

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

with Federation

several options for horizontal partitioning and Sharding

none

Sharding

making use of Hadoop

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

selectable replication factor

making use of Hadoop

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

not for MyISAM storage engine

ACID

but no files for transaction logging

Atomic updates per row, document, or graph entity

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

but no files for transaction 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

with MEMORY storage engine

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

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

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

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

News

How a Neuro-Symbolic AI Approach Can Improve Trust in AI Apps
23 May 2024

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

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.