DBMS > Amazon Redshift vs. Apache Drill vs. CouchDB vs. Firebase Realtime Database

System Properties Comparison Amazon Redshift vs. Apache Drill vs. CouchDB vs. Firebase Realtime Database

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Document store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Website

aws.amazon.com/redshift

drill.apache.org

couchdb.apache.org

firebase.google.com/products/realtime-database

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.couchdb.org/en/stable

firebase.google.com/docs/database

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

acquired by Google 2014

Initial release

2012

2005

2012

Current release

1.20.3, January 2023

3.3.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache version 2

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

Erlang

Server operating systems

hosted

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

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

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

Android
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java
JavaScript
Objective-C

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

View functions in JavaScript

limited functionality with using 'rules'

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

atomic operations within a single document possible

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Access rights for users can be defined per database

yes, based on authentication and database rules

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.