DBMS > Google Cloud Firestore vs. Interbase vs. PostGIS vs. SQLite

System Properties Comparison Google Cloud Firestore vs. Interbase vs. PostGIS vs. SQLite

Please select another system to include it in the comparison.

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.

Light-weight proven RDBMS

originally from Borland

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/firestore

www.embarcadero.com/products/interbase

postgis.net

www.sqlite.org

Technical documentation

firebase.google.com/docs/firestore

docs.embarcadero.com/products/interbase

postgis.net/documentation

www.sqlite.org/docs.html

Developer

Google

Embarcadero

Dwayne Richard Hipp

Initial release

2017

1984

2005

2000

Current release

InterBase 2020, December 2019

3.4.2, February 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

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

Server operating systems

hosted

Android
iOS
Linux
OS X
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.

export as XML data possible

yes

Secondary indexes

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

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Interbase Change Views

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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.

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.