DBMS > Amazon DynamoDB vs. Apache Druid vs. Coveo vs. IBM Cloudant

System Properties Comparison Amazon DynamoDB vs. Apache Druid vs. Coveo vs. IBM Cloudant

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Database as a Service offering based on Apache CouchDB

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Search engine

Document store

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	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	2.75
Rank	#104	Overall
	#19	Document stores

Website

aws.amazon.com/dynamodb

druid.apache.org

www.coveo.com

www.ibm.com/products/cloudant

Technical documentation

docs.aws.amazon.com/dynamodb

druid.apache.org/docs/latest/design

docs.coveo.com

cloud.ibm.com/docs/Cloudant

Developer

Amazon

Apache Software Foundation and contributors

Coveo

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2012

2010

Current release

29.0.1, April 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache license v2

commercial

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

Erlang

Server operating systems

hosted

Linux
OS X
Unix

hosted

Data scheme

schema-free

yes

schema-less columns are supported

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

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

SQL

Support of SQL

SQL for querying

APIs and other access methods

RESTful HTTP API

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

yes

Multi-source replication
Source-replica replication

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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

Durability

Support for making data persistent

yes

In-memory capabilities

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

User concepts

Access control

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

granular access controls, API key management, content filters

Access rights for users can be defined per database

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.