DBMS > Amazon Neptune vs. Amazon Redshift vs. Datomic vs. Microsoft Access

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. Datomic vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Graph DBMS
RDF store

Relational DBMS

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

www.datomic.com

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

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

docs.datomic.com

developer.microsoft.com/en-us/access

Developer

Amazon

Amazon (based on PostgreSQL)

Cognitect

Microsoft

Initial release

2017

2012

1992

Current release

1.0.6735, June 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

limited edition free

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

C++

Server operating systems

hosted

All OS with a Java VM

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

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

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

Clojure
Java

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

since Access 2010 using the ACE-engine

Triggers

By using transaction functions

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

But extensive use of caching in the application peers

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

none

But extensive use of caching in the application peers

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

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.