DBMS > Amazon Redshift vs. etcd vs. Geode vs. Google Cloud Firestore

System Properties Comparison Amazon Redshift vs. etcd vs. Geode vs. Google Cloud Firestore

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Primary database model

Relational DBMS

Key-value store

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Website

aws.amazon.com/redshift

etcd.io
github.com/etcd-io/etcd

geode.apache.org

firebase.google.com/products/firestore

Technical documentation

docs.aws.amazon.com/redshift

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

geode.apache.org/docs

firebase.google.com/docs/firestore

Developer

Amazon (based on PostgreSQL)

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Initial release

2012

2002

2017

Current release

3.4, August 2019

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

the JDK (8 or later) is also required

hosted

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

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC

gRPC
JSON over HTTP

Java Client API
Memcached protocol
RESTful HTTP API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
All JVM based languages
C++
Groovy
Java
Scala

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes, Firebase Rules & Cloud Functions

Triggers

yes, watching key changes

yes

Cache Event Listeners

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

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, on a single node

yes

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

Access rights per client and object definable

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.