DBMS > Amazon CloudSearch vs. Drizzle vs. Microsoft Azure Cosmos DB vs. RocksDB

System Properties Comparison Amazon CloudSearch vs. Drizzle vs. Microsoft Azure Cosmos DB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Search engine

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

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

Website

aws.amazon.com/cloudsearch

azure.microsoft.com/services/cosmos-db

rocksdb.org

Technical documentation

docs.aws.amazon.com/cloudsearch

learn.microsoft.com/azure/cosmos-db

github.com/facebook/rocksdb/wiki

Developer

Amazon

Drizzle project, originally started by Brian Aker

Microsoft

Facebook, Inc.

Initial release

2012

2008

2014

2013

Current release

7.2.4, September 2012

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

HTTP API

JDBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

Triggers

hooks for callbacks inside the server can be used.

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

yes

Concurrency

Support for concurrent manipulation of data

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights can be defined down to the item level

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.