DBMS > Amazon DynamoDB vs. Elasticsearch vs. KeyDB vs. Microsoft Access vs. Tarantool

System Properties Comparison Amazon DynamoDB vs. Elasticsearch vs. KeyDB vs. Microsoft Access vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store

Search engine

Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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	132.83
Rank	#7	Overall
	#1	Search engines

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

aws.amazon.com/dynamodb

www.elastic.co/elasticsearch

github.com/Snapchat/KeyDB
keydb.dev

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

www.tarantool.io

Technical documentation

docs.aws.amazon.com/dynamodb

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

docs.keydb.dev

developer.microsoft.com/en-us/access

www.tarantool.io/en/doc

Developer

Amazon

Elastic

EQ Alpha Technology Ltd.

Microsoft

Initial release

2012

2010

2019

1992

2008

Current release

8.6, January 2023

1902 (16.0.11328.20222), March 2019

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Elastic License

Open Source

BSD-3

commercial

Bundled with Microsoft Office

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C++

C and C++

Server operating systems

hosted

All OS with a Java VM

Linux

Windows

Not a real database server, but making use of DLLs

BSD
Linux
macOS

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

All search fields are automatically indexed

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
DAO
ODBC
OLE DB

Open binary protocol

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Lua

yes

since Access 2010 using the ACE-engine

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes

by using the 'percolation' feature

yes

since Access 2010 using the ACE-engine

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
Strong eventual consistency with CRDTs

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

but no files for transaction logging

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

but no files for transaction logging

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

simple password-based access control and ACL

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.