DBMS > Amazon Aurora vs. Drizzle vs. Elasticsearch vs. RocksDB

System Properties Comparison Amazon Aurora vs. Drizzle vs. Elasticsearch 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

MySQL and PostgreSQL compatible cloud service by Amazon

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

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

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

Primary database model

Relational DBMS

Search engine

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS
Vector DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

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

Website

aws.amazon.com/rds/aurora

www.elastic.co/elasticsearch

rocksdb.org

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

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

github.com/facebook/rocksdb/wiki

Developer

Amazon

Drizzle project, originally started by Brian Aker

Elastic

Facebook, Inc.

Initial release

2015

2008

2010

2013

Current release

7.2.4, September 2012

8.6, January 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Elastic License

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

Java

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

All OS with a Java VM

Linux

Data scheme

yes

schema-free

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

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.

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC

Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PHP

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.