DBMS > Google Cloud Firestore vs. Heroic vs. RocksDB vs. Yanza

System Properties Comparison Google Cloud Firestore vs. Heroic vs. RocksDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded 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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Time Series DBMS for IoT Applications

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

firebase.google.com/products/firestore

github.com/spotify/heroic

rocksdb.org

yanza.com

Technical documentation

firebase.google.com/docs/firestore

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Google

Spotify

Facebook, Inc.

Yanza

Initial release

2017

2014

2013

2015

Current release

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

Linux

Windows

Data scheme

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.

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

HTTP API

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes, with Cloud Functions

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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.

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.