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

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

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

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

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.

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

Titan is a Graph DBMS optimized for distributed clusters.

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

firebase.google.com/products/firestore

www.snowflake.com

github.com/bytedance/terarkdb

github.com/thinkaurelius/titan

yaacomo.com

Technical documentation

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

github.com/thinkaurelius/titan/wiki

Developer

Google

Snowflake Computing Inc.

ByteDance, originally Terark

Aurelius, owned by DataStax

Q2WEB GmbH

Initial release

2017

2014

2016

2012

2009

License

Commercial or Open Source

commercial

restricted open source version available

Open Source

Apache license, 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++

Java

Server operating systems

hosted

Linux
OS X
Unix
Windows

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

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

CLI Client
JDBC
ODBC

C++ API
Java API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java

Clojure
Java
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

yes

Triggers

yes, with Cloud Functions

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

yes

via pluggable storage backends

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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.

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

User authentification and security via Rexster Graph Server

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.