DBMS > Amazon DocumentDB vs. Amazon Redshift vs. Fujitsu Enterprise Postgres vs. Microsoft Access

System Properties Comparison Amazon DocumentDB vs. Amazon Redshift vs. Fujitsu Enterprise Postgres vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service for use with business intelligence tools

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

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

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.31
Rank	#285	Overall
	#129	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/documentdb

aws.amazon.com/redshift

www.postgresql.fastware.com

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

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/redshift

www.postgresql.fastware.com/product-manuals

developer.microsoft.com/en-us/access

Developer

Amazon (based on PostgreSQL)

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Microsoft

Initial release

2019

2012

1992

Current release

Fujitsu Enterprise Postgres 14, January 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

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

C++

Server operating systems

hosted

Linux
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

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.

Secondary indexes

yes

restricted

yes

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

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

partitioning by range, list and by hash

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

informational only, not enforced by the system

yes

Transaction concepts

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

Atomic single-document operations

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Access rights for users and roles

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

100% compatible with community PostgreSQL
» more

Competitive advantages

Built-in TDE and Data Masking security. In-Memory Columnar Index, and a high speed...
» more

Typical application scenarios

Transactional payments applications, reporting and mixed workloads.
» more

Market metrics

Over 30 years experience in database technology. Over 20 years in Postgres development...
» more

Licensing and pricing models

Core based licensing
» 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.