DBMS > Google Cloud Firestore vs. Heroic vs. Microsoft Azure Cosmos DB vs. Oracle Berkeley DB vs. RocksDB

System Properties Comparison Google Cloud Firestore vs. Heroic vs. Microsoft Azure Cosmos DB vs. Oracle Berkeley DB 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.

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

Globally distributed, horizontally scalable, multi-model database service

Widely used in-process key-value store

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

Primary database model

Document store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Spatial DBMS

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

firebase.google.com/products/firestore

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

Technical documentation

firebase.google.com/docs/firestore

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

Developer

Google

Spotify

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Initial release

2017

2014

1994

2013

Current release

18.1.40, May 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

commercial license available

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, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

only with the Berkeley DB XML edition

Secondary indexes

yes

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

SQL interfaced based on SQLite is available

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

C++ API
Java API

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

JavaScript

Triggers

yes, with Cloud Functions

JavaScript

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

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.

Access rights can be defined down to the item level

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.