DBMS > Amazon Redshift vs. Elasticsearch vs. Firebase Realtime Database vs. Graphite

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. Firebase Realtime Database vs. Graphite

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	128.79
Rank	#8	Overall
	#1	Search engines

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

firebase.google.com/products/realtime-database

github.com/graphite-project/graphite-web

Technical documentation

docs.aws.amazon.com/redshift

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

firebase.google.com/docs/database

graphite.readthedocs.io

Developer

Amazon (based on PostgreSQL)

Elastic

Google

acquired by Google 2014

Chris Davis

Initial release

2012

2010

2012

2006

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

commercial

Open Source

Apache 2.0

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

Java

Python

Server operating systems

hosted

All OS with a Java VM

hosted

Linux
Unix

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
Sockets

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

limited functionality with using 'rules'

Triggers

yes

by using the 'percolation' feature

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

none

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

yes

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

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.