DBMS > Google Cloud Firestore vs. IBM Cloudant vs. JaguarDB vs. SQLite vs. XTDB

System Properties Comparison Google Cloud Firestore vs. IBM Cloudant vs. JaguarDB vs. SQLite vs. XTDB

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.

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Key-value store
Vector DBMS

Relational DBMS

Document store

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

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

firebase.google.com/products/firestore

www.ibm.com/products/cloudant

www.jaguardb.com

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

firebase.google.com/docs/firestore

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2017

2010

2015

2000

2019

Current release

3.3 July 2023

3.46.1 (13 August 2024), August 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Public Domain

Open Source

MIT License

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

Erlang

C++

the server part. Clients available in other languages

Clojure

Server operating systems

hosted

Linux

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

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

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Clojure
Java

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

Multi-source replication
Source-replica replication

Multi-source replication

none

yes, each node contains all data

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

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

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

rights management via user accounts

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.