DBMS > Amazon DocumentDB vs. Amazon Redshift vs. Drizzle vs. etcd vs. Google Cloud Firestore

System Properties Comparison Amazon DocumentDB vs. Amazon Redshift vs. Drizzle vs. etcd vs. Google Cloud Firestore

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service for use with business intelligence tools

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A distributed reliable key-value store

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

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Website

aws.amazon.com/documentdb

aws.amazon.com/redshift

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

firebase.google.com/products/firestore

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/redshift

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

firebase.google.com/docs/firestore

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Google

Initial release

2019

2012

2008

2017

Current release

7.2.4, September 2012

3.4, August 2019

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2.0

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

Server operating systems

hosted

FreeBSD
Linux
OS X

FreeBSD
Linux
Windows

experimental

hosted

Data scheme

schema-free

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

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

JDBC

gRPC
JSON over HTTP

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

C
C++
Java
PHP

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

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes, Firebase Rules & Cloud Functions

Triggers

hooks for callbacks inside the server can be used.

yes, watching key changes

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication
Source-replica replication

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

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

informational only, not enforced by the system

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-document operations

ACID

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.