DBMS > Amazon Redshift vs. Firebase Realtime Database vs. Geode vs. NuoDB vs. PouchDB

System Properties Comparison Amazon Redshift vs. Firebase Realtime Database vs. Geode vs. NuoDB vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

NuoDB is a webscale distributed database that supports SQL and ACID transactions

JavaScript DBMS with an API inspired by CouchDB

Primary database model

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	0.87
Rank	#201	Overall
	#94	Relational DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

firebase.google.com/products/realtime-database

geode.apache.org

www.3ds.com/nuodb-distributed-sql-database

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

geode.apache.org/docs

doc.nuodb.com

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Dassault Systèmes

originally NuoDB, Inc.

Apache Software Foundation

Initial release

2012

2002

2013

2012

Current release

1.1, February 2017

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

limited edition free

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

C++

JavaScript

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

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

Data scheme

yes

schema-free

yes

schema-free

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.

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

user defined functions

Java, SQL

View functions in JavaScript

Triggers

Callbacks are triggered when data changes

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

data is dynamically stored/cached on the nodes where it is read/written

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Managed transparently by NuoDB

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Immediate Consistency

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

yes

yes, on a single node

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Temporary table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights per client and object definable

Standard SQL roles/ privileges, Administrative Users

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.