DBMS > Amazon Redshift vs. Citus vs. Firebase Realtime Database vs. Infobright

System Properties Comparison Amazon Redshift vs. Citus vs. Firebase Realtime Database vs. Infobright

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Website

aws.amazon.com/redshift

www.citusdata.com

firebase.google.com/products/realtime-database

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

firebase.google.com/docs/database

Developer

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2012

2010

2012

2005

Current release

8.1, December 2018

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Server operating systems

hosted

Linux

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

restricted

yes

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Java
JavaScript
Objective-C

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

limited functionality with using 'rules'

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

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

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.