DBMS > Amazon DynamoDB vs. Ehcache vs. Faircom EDGE vs. Microsoft Access

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. Faircom EDGE vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A widely adopted Java cache with tiered storage options

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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
Key-value store

Key-value store

Key-value store
Relational DBMS

Relational DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/dynamodb

www.ehcache.org

www.faircom.com/products/faircom-edge

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

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

developer.microsoft.com/en-us/access

Developer

Amazon

Terracotta Inc, owned by Software AG

FairCom Corporation

Microsoft

Initial release

2012

2009

1979

1992

Current release

3.10.0, March 2022

V3, October 2020

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

commercial

Restricted, free version available

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

ANSI C, C++

C++

Server operating systems

hosted

All OS with a Java VM

Android
Linux

ARM, x86
Raspbian
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

but not compliant to any SQL standard

APIs and other access methods

RESTful HTTP API

JCache

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

since Access 2010 using the ACE-engine

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

File partitioning

Customizable business rules for partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

Synchronous and asynchronous realtime replication based on transaction logs

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes

supports JTA and can work as an XA resource

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 can be defined via the AWS Identity and Access Management (IAM)

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.