DBMS > Amazon Redshift vs. OrigoDB vs. PouchDB vs. Quasardb

System Properties Comparison Amazon Redshift vs. OrigoDB vs. PouchDB vs. Quasardb

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

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Document store

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/redshift

origodb.com

pouchdb.com

quasar.ai

Technical documentation

docs.aws.amazon.com/redshift

origodb.com/docs

pouchdb.com/guides

doc.quasar.ai/master

Developer

Amazon (based on PostgreSQL)

Robert Friberg et al

Apache Software Foundation

quasardb

Initial release

2012

2009

under the name LiveDB

2012

2009

Current release

7.1.1, June 2019

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

hosted

Linux
Windows

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

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

integer and binary

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.

can be achieved using .NET

Secondary indexes

restricted

yes

via views

yes

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net

JavaScript

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes

View functions in JavaScript

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

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

Write ahead log

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

Cryptographically strong user authentication and audit trail

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.