DBMS > Google Cloud Firestore vs. PouchDB vs. SQLite vs. STSdb vs. VoltDB

System Properties Comparison Google Cloud Firestore vs. PouchDB vs. SQLite vs. STSdb vs. VoltDB

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.

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

firebase.google.com/products/firestore

pouchdb.com

www.sqlite.org

github.com/STSSoft/STSdb4

www.voltdb.com

Technical documentation

firebase.google.com/docs/firestore

pouchdb.com/guides

www.sqlite.org/docs.html

docs.voltdb.com

Developer

Google

Apache Software Foundation

Dwayne Richard Hipp

STS Soft SC

VoltDB Inc.

Initial release

2017

2012

2000

2011

2010

Current release

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

4.0.8, September 2015

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

GPLv2, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

JavaScript

Java, C++

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Windows

Linux
OS X

for development

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

primitive types and user defined types (classes)

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 views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

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

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript

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

C#
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

View functions in JavaScript

Java

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Snapshots and command logging

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.

Users and roles with access to stored procedures

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.