DBMS > Derby vs. FatDB vs. Google Cloud Firestore vs. PouchDB vs. SQLite

System Properties Comparison Derby vs. FatDB vs. Google Cloud Firestore vs. PouchDB vs. SQLite

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

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

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

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

Website

db.apache.org/derby

firebase.google.com/products/firestore

pouchdb.com

www.sqlite.org

Technical documentation

db.apache.org/derby/manuals/index.html

firebase.google.com/docs/firestore

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Apache Software Foundation

FatCloud

Google

Apache Software Foundation

Dwayne Richard Hipp

Initial release

1997

2012

2017

2012

2000

Current release

10.17.1.0, November 2023

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache version 2

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

JavaScript

Server operating systems

All OS with a Java VM

Windows

hosted

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

server-less

Data scheme

yes

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Supported programming languages

Java

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

View functions in JavaScript

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.