DBMS > Amazon Redshift vs. Firebird vs. Google Cloud Spanner vs. PouchDB

System Properties Comparison Amazon Redshift vs. Firebird vs. Google Cloud Spanner 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

Firebird is an open source RDBMS forked from Borland's InterBase

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

www.firebirdsql.org

cloud.google.com/spanner

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.firebirdsql.org/en/reference-manuals

cloud.google.com/spanner/docs

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Firebird Foundation

Google

Apache Software Foundation

Initial release

2012

2000

As fork of Borland's InterBase

2017

2012

Current release

5.0.0, January 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

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

C and C++

JavaScript

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

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

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

APIs and other access methods

JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

PSQL

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication with 3 replicas for regional instances.

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

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.