DBMS > Amazon Aurora vs. Apache Drill vs. Memcached vs. PouchDB vs. Snowflake

System Properties Comparison Amazon Aurora vs. Apache Drill vs. Memcached vs. PouchDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

In-memory key-value store, originally intended for caching

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Key-value store

Document store

Relational DBMS

Secondary database models

Document store

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

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

drill.apache.org/docs

github.com/memcached/memcached/wiki

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Amazon

Apache Software Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2015

2012

2003

2012

2014

Current release

1.20.3, January 2023

1.6.25, March 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

BSD license

Open Source

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

JavaScript

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

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

via views

SQL

Support of SQL

yes

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

HTTP REST

only for PouchDB Server
JavaScript 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

C++

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

yes

using SASL (Simple Authentication and Security Layer) protocol

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.