DBMS > Google Cloud Firestore vs. Memcached vs. Microsoft Azure Table Storage vs. Snowflake

System Properties Comparison Google Cloud Firestore vs. Memcached vs. Microsoft Azure Table Storage vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

Primary database model

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/firestore

www.memcached.org

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

Technical documentation

firebase.google.com/docs/firestore

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Snowflake Computing Inc.

Initial release

2017

2003

2012

2014

Current release

1.6.25, March 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

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

Server operating systems

hosted

FreeBSD
Linux
OS X
Unix
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

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
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

optimistic locking

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.

User concepts

Access control

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights based on private key authentication or shared access signatures

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.