DBMS > Amazon DynamoDB vs. Interbase vs. Memcached vs. Microsoft Access

System Properties Comparison Amazon DynamoDB vs. Interbase vs. Memcached 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

Light-weight proven RDBMS

originally from Borland

In-memory key-value store, originally intended for caching

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

Relational DBMS

Key-value store

Relational DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	5.04
Rank	#71	Overall
	#39	Relational DBMS

Score	20.74
Rank	#32	Overall
	#4	Key-value stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Website

aws.amazon.com/dynamodb

www.embarcadero.com/products/interbase

www.memcached.org

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

Technical documentation

docs.aws.amazon.com/dynamodb

docs.embarcadero.com/products/interbase

github.com/memcached/memcached/wiki

developer.microsoft.com/en-us/access

Developer

Amazon

Embarcadero

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Initial release

2012

1984

2003

1992

Current release

InterBase 2020, December 2019

1.6.25, March 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

BSD license

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

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

schema-free

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

yes

by integration with AWS Lambda

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Interbase Change Views

none

Repcached, a Memcached patch, provides this functionallity

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

Immediate Consistency

Foreign keys

Referential integrity

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

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.