DBMS > Google Cloud Firestore vs. Hazelcast vs. Heroic vs. Linter vs. RocksDB

System Properties Comparison Google Cloud Firestore vs. Hazelcast vs. Heroic vs. Linter vs. RocksDB

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.

A widely adopted in-memory data grid

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

RDBMS for high security requirements

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

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

Website

firebase.google.com/products/firestore

hazelcast.com

github.com/spotify/heroic

linter.ru

rocksdb.org

Technical documentation

firebase.google.com/docs/firestore

hazelcast.org/imdg/docs

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Google

Hazelcast

Spotify

relex.ru

Facebook, Inc.

Initial release

2017

2008

2014

1990

2013

Current release

5.3.6, November 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Open Source

BSD

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

Java

C and C++

C++

Server operating systems

hosted

All OS with a Java VM

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Data scheme

schema-free

yes

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

the object must implement a serialization strategy

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

JCache
JPA
Memcached protocol
RESTful HTTP API

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

Supported programming languages

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

Event Listeners, Executor Services

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes, with Cloud Functions

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Replicated Map

yes

Source-replica replication

yes

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

one or two-phase-commit; repeatable reads; read commited

ACID

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.

Role-based access control

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.