DBMS > Amazon Redshift vs. eXtremeDB vs. FatDB vs. Microsoft Access

System Properties Comparison Amazon Redshift vs. eXtremeDB vs. FatDB vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Natively in-memory DBMS with options for persistency, high-availability and clustering

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Relational DBMS

Relational DBMS
Time Series DBMS

Document store
Key-value store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.80
Rank	#214	Overall
	#99	Relational DBMS
	#18	Time Series DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/redshift

www.mcobject.com

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

Technical documentation

docs.aws.amazon.com/redshift

www.mcobject.com/docs/extremedb.htm

developer.microsoft.com/en-us/access

Developer

Amazon (based on PostgreSQL)

McObject

FatCloud

Microsoft

Initial release

2012

2001

2012

1992

Current release

8.2, 2021

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

C++

Server operating systems

hosted

AIX
HP-UX
Linux
macOS
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

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.

support of XML interfaces available

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with the option: eXtremeSQL

Via inetgration in SQL Server

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Java
Lua
Python
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

yes

since Access 2010 using the ACE-engine

Triggers

yes

by defining events

yes

via applications

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning / sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

selectable replication factor

none

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

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» 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.