DBMS > Amazon CloudSearch vs. Apache Druid vs. EJDB vs. IBM Cloudant vs. RocksDB

System Properties Comparison Amazon CloudSearch vs. Apache Druid vs. EJDB vs. IBM Cloudant vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A hosted search engine 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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Database as a Service offering based on Apache CouchDB

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Search engine

Relational DBMS
Time Series DBMS

Document store

Key-value store

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

aws.amazon.com/cloudsearch

druid.apache.org

github.com/Softmotions/ejdb

www.ibm.com/products/cloudant

rocksdb.org

Technical documentation

docs.aws.amazon.com/cloudsearch

druid.apache.org/docs/latest/design

github.com/Softmotions/ejdb/blob/master/README.md

cloud.ibm.com/docs/Cloudant

github.com/facebook/rocksdb/wiki

Developer

Amazon

Apache Software Foundation and contributors

Softmotions

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Facebook, Inc.

Initial release

2012

2010

2013

Current release

29.0.1, April 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

GPLv2

commercial

Open Source

BSD

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

C++

Server operating systems

hosted

Linux
OS X
Unix

server-less

hosted

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

SQL for querying

APIs and other access methods

HTTP API

JDBC
RESTful HTTP/JSON API

in-process shared library

RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

manual/auto, time-based

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes, via HDFS, S3 or other storage engines

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

atomic operations within a document possible

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Optimistic locking

yes

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.

yes

User concepts

Access control

authentication via encrypted signatures

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

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.