DBMS > Google Cloud Firestore vs. Heroic vs. IBM Cloudant vs. LMDB vs. SQLite

System Properties Comparison Google Cloud Firestore vs. Heroic vs. IBM Cloudant vs. LMDB vs. SQLite

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

Database as a Service offering based on Apache CouchDB

A high performant, light-weight, embedded key-value database library

Widely used embeddable, in-process RDBMS

Primary database model

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	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/firestore

github.com/spotify/heroic

www.ibm.com/products/cloudant

www.symas.com/symas-embedded-database-lmdb

www.sqlite.org

Technical documentation

firebase.google.com/docs/firestore

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

www.lmdb.tech/doc

www.sqlite.org/docs.html

Developer

Google

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Symas

Dwayne Richard Hipp

Initial release

2017

2014

2010

2011

2000

Current release

0.9.32, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Erlang

Server operating systems

hosted

Linux
Unix
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

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

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

View functions (Map-Reduce) in JavaScript

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

none

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

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

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 for users can be defined per database

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.