DBMS > AllegroGraph vs. Amazon Redshift vs. BaseX vs. Microsoft Access

System Properties Comparison AllegroGraph vs. Amazon Redshift vs. BaseX vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service for use with business intelligence tools

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Native XML DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

allegrograph.com

aws.amazon.com/redshift

basex.org

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

Technical documentation

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

docs.aws.amazon.com/redshift

docs.basex.org

developer.microsoft.com/en-us/access

Developer

Franz Inc.

Amazon (based on PostgreSQL)

BaseX GmbH

Microsoft

Initial release

2004

2012

2007

1992

Current release

8.0, December 2023

10.7, August 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

BSD license

commercial

Bundled with Microsoft Office

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

RDF schemas

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

XQuery supports types

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

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SPARQL is used as query language

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

APIs and other access methods

RESTful HTTP API
SPARQL

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

All languages supporting JDBC/ODBC

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

Triggers

yes

via events

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

multiple readers, single writer

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept on 4 levels

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

More information provided by the system vendor

Specific characteristics

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

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» 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.