DBMS > Google Cloud Firestore vs. Riak KV vs. Snowflake vs. TerarkDB

System Properties Comparison Google Cloud Firestore vs. Riak KV vs. Snowflake vs. TerarkDB

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.

Distributed, fault tolerant key-value store

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Key-value store

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

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

firebase.google.com/products/firestore

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

firebase.google.com/docs/firestore

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2017

2009

2014

2016

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

restricted open source version available

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

Erlang

C++

Server operating systems

hosted

Linux
OS X

hosted

Data scheme

schema-free

yes

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

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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

APIs and other access methods

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

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Erlang

user defined functions

Triggers

yes, with Cloud Functions

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

yes

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.

yes

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 Riak Security

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.