DBMS > Amazon Aurora vs. PouchDB vs. Snowflake vs. Splunk vs. Valentina Server

System Properties Comparison Amazon Aurora vs. PouchDB vs. Snowflake vs. Splunk vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

JavaScript DBMS with an API inspired by CouchDB

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

Analytics Platform for Big Data

Object-relational database and reports server

Primary database model

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	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

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

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Amazon

Apache Software Foundation

Snowflake Computing Inc.

Splunk Inc.

Paradigma Software

Initial release

2015

2012

2014

2003

1999

Current release

7.1.1, June 2019

5.7.5

License

Commercial or Open Source

commercial

Open Source

commercial

Limited free edition and free developer edition available

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

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

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

yes

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

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

HTTP REST

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

JavaScript

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users and roles

fine grained access rights according to SQL-standard

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.