DBMS > Firebase Realtime Database vs. Memcached vs. RethinkDB vs. Snowflake

System Properties Comparison Firebase Realtime Database vs. Memcached vs. RethinkDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory key-value store, originally intended for caching

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.memcached.org

rethinkdb.com

www.snowflake.com

Technical documentation

firebase.google.com/docs/database

github.com/memcached/memcached/wiki

rethinkdb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Google

acquired by Google 2014

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

The Linux Foundation

since July 2017

Snowflake Computing Inc.

Initial release

2012

2003

2009

2014

Current release

1.6.25, March 2024

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache Version 2

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
Unix
Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

Callbacks are triggered when data changes

Client-side triggers through changefeeds

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

range based

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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.

User concepts

Access control

yes, based on authentication and database rules

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

users and table-level permissions

Users with fine-grained authorization concept, user roles and pluggable authentication

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.