DBMS > Google Cloud Firestore vs. PostGIS vs. SpaceTime vs. Sphinx

System Properties Comparison Google Cloud Firestore vs. PostGIS vs. SpaceTime vs. Sphinx

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.

Spatial extension of PostgreSQL

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store

Spatial DBMS

Search engine

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	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

firebase.google.com/products/firestore

postgis.net

www.mireo.com/spacetime

sphinxsearch.com

Technical documentation

firebase.google.com/docs/firestore

postgis.net/documentation

sphinxsearch.com/docs

Developer

Google

Mireo

Sphinx Technologies Inc.

Initial release

2017

2005

2020

2001

Current release

3.4.2, February 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

hosted

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

SQL-like query language (SphinxQL)

APIs and other access methods

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

RESTful HTTP API

Proprietary protocol

Supported programming languages

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

C#
C++
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Fixed-grid hypercubes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

based on PostgreSQL

Real-time block device replication (DRBD)

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

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

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.

yes

based on PostgreSQL

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to Choose
8 March 2024, Appinventiv

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

NoSQL on the Cloud With Python
7 August 2020, Towards Data Science

Google Launches Cloud NoSQL Database for Mobile, Web Apps
10 October 2017, ADT Magazine

provided by Google News

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose?
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018
22 December 2018, WQXR Radio

Here’s Why Russia Is Cracking Down on Google
23 February 2015, TIME

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

provided by Google News

Share this page