DBMS > Amazon Redshift vs. EventStoreDB vs. Oracle NoSQL vs. PouchDB

System Properties Comparison Amazon Redshift vs. EventStoreDB vs. Oracle NoSQL vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Industrial-strength, open-source database solution built from the ground up for event sourcing.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Event Store

Document store
Key-value store
Relational DBMS

Document store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

www.eventstore.com

www.oracle.com/database/nosql/technologies/nosql

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

developers.eventstore.com

docs.oracle.com/en/database/other-databases/nosql-database/index.html

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Event Store Limited

Oracle

Apache Software Foundation

Initial release

2012

2011

2012

Current release

21.2, February 2021

24.1, May 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

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

JavaScript

Server operating systems

hosted

Linux
Windows

Linux
Solaris SPARC/x86

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

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.