DBMS > Amazon Aurora vs. Elasticsearch vs. EXASOL vs. IBM Cloudant vs. Snowflake

System Properties Comparison Amazon Aurora vs. Elasticsearch vs. EXASOL vs. IBM Cloudant vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Database as a Service offering based on Apache CouchDB

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/rds/aurora

www.elastic.co/elasticsearch

www.exasol.com

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

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

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

www.exasol.com/resources

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Amazon

Elastic

Exasol

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2015

2010

2000

2010

2014

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

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

All OS with a Java VM

hosted

Data scheme

yes

schema-free

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

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

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

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

Java
Lua
Python
R

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

yes

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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.