DBMS > Google Cloud Datastore vs. Google Cloud Firestore vs. Snowflake vs. TerarkDB vs. Yaacomo

System Properties Comparison Google Cloud Datastore vs. Google Cloud Firestore vs. Snowflake vs. TerarkDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

cloud.google.com/datastore

firebase.google.com/products/firestore

www.snowflake.com

github.com/bytedance/terarkdb

yaacomo.com

Technical documentation

cloud.google.com/datastore/docs

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Snowflake Computing Inc.

ByteDance, originally Terark

Q2WEB GmbH

Initial release

2008

2017

2014

2016

2009

License

Commercial or Open Source

commercial

restricted open source version available

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

Android
Linux
Windows

Data scheme

schema-free

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

CLI Client
JDBC
ODBC

C++ API
Java API

JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

using Google App Engine

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes, with Cloud Functions

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 (IAM)

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

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

fine grained access rights according to SQL-standard

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.