DBMS > Amazon Redshift vs. Firebird vs. IBM Cloudant vs. RavenDB

System Properties Comparison Amazon Redshift vs. Firebird vs. IBM Cloudant vs. RavenDB

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

Database as a Service offering based on Apache CouchDB

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

www.firebirdsql.org

www.ibm.com/products/cloudant

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

www.firebirdsql.org/en/reference-manuals

cloud.ibm.com/docs/Cloudant

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Firebird Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Hibernating Rhinos

Initial release

2012

2000

As fork of Borland's InterBase

2010

Current release

5.0.0, January 2024

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

Open Source

AGPL version 3, commercial license available

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++

Erlang

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux
macOS
Raspberry Pi
Windows

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in Python

PSQL

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

atomic operations within a document possible

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

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

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

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 can be defined per database

Authorization levels configured per client per database

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.