DBMS > Amazon DynamoDB vs. Coveo vs. EsgynDB vs. MaxDB vs. PouchDB

System Properties Comparison Amazon DynamoDB vs. Coveo vs. EsgynDB vs. MaxDB vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A robust and reliable RDBMS optimized to run all major SAP solutions

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store
Key-value store

Search engine

Relational DBMS

Document store

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

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

docs.coveo.com

maxdb.sap.com/documentation

pouchdb.com/guides

Developer

Amazon

Coveo

Esgyn

SAP, acquired from Software AG (Adabas-D) in 1997

Apache Software Foundation

Initial release

2012

2015

1984

2012

Current release

7.9.10.12, February 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Limited community edition free

Open Source

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

C++

JavaScript

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

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.

Secondary indexes

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
Java
Perl
PHP
Python

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

yes

View functions in JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual 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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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)

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

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.