DBMS > Amazon Redshift vs. Apache Phoenix vs. Faircom DB vs. PouchDB

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Faircom DB 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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

phoenix.apache.org

www.faircom.com/products/faircom-db

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

phoenix.apache.org

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

FairCom Corporation

Apache Software Foundation

Initial release

2012

2014

1979

2012

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

V12, November 2020

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Restricted, free version available

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

ANSI C, C++

JavaScript

Server operating systems

hosted

Linux
Unix
Windows

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

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

Data scheme

yes

late-bound, schema-on-read capabilities

schema free, schema optional, schema required, partial schema,

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

yes

yes, ANSI SQL with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

.Net, JavaScript, C/C++

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Fine grained access rights according to SQL-standard with additional protections for files

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.