DBMS > Amazon Redshift vs. EsgynDB vs. Firebase Realtime Database vs. Google Cloud Bigtable vs. Netezza

System Properties Comparison Amazon Redshift vs. EsgynDB vs. Firebase Realtime Database vs. Google Cloud Bigtable vs. Netezza

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Relational DBMS

Document store

Key-value store
Wide column store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Website

aws.amazon.com/redshift

www.esgyn.cn

firebase.google.com/products/realtime-database

cloud.google.com/bigtable

www.ibm.com/products/netezza

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

cloud.google.com/bigtable/docs

Developer

Amazon (based on PostgreSQL)

Esgyn

Google

acquired by Google 2014

Google

IBM

Initial release

2012

2015

2012

2015

2000

License

Commercial or Open Source

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

C++, Java

Server operating systems

hosted

Linux

hosted

Linux

included in appliance

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

Java
JavaScript
Objective-C

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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

Atomic single-row operations

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

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

Users with fine-grained authorization concept

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.