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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

Primary database model

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

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

basex.org

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

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

developer.microsoft.com/en-us/access

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

BaseX GmbH

Microsoft

Apache Software Foundation

Initial release

2012

2007

1992

2012

Current release

10.7, August 2023

1902 (16.0.11328.20222), March 2019

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Bundled with Microsoft Office

Open Source

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++

JavaScript

Server operating systems

hosted

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

schema-free

yes

schema-free

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.

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

Triggers

yes

via events

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

yes

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

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

yes

User concepts

Access control

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

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.