DBMS > Amazon Redshift vs. Datomic vs. Microsoft Access vs. NSDb vs. Riak KV

System Properties Comparison Amazon Redshift vs. Datomic vs. Microsoft Access vs. NSDb vs. Riak KV

Editorial information provided by DB-Engines

Name

Description

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.datomic.com

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

nsdb.io

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

developer.microsoft.com/en-us/access

nsdb.io/Architecture

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon (based on PostgreSQL)

Cognitect

Microsoft

OpenSource, formerly Basho Technologies

Initial release

2012

1992

2017

2009

Current release

1.0.6735, June 2023

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

License

Commercial or Open Source

commercial

limited edition free

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Java, Scala

Erlang

Server operating systems

hosted

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Linux
macOS

Linux
OS X

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

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

Java
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

since Access 2010 using the ACE-engine

Erlang

Triggers

By using transaction functions

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

none

selectable replication factor

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

links between data sets can be stored

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

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

yes

but no files for transaction logging

Using Apache Lucene

yes

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

fine grained access rights according to SQL-standard

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

yes, using Riak Security

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.