DBMS > Google Cloud Firestore vs. Neo4j vs. SQLite

System Properties Comparison Google Cloud Firestore vs. Neo4j 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.

Scalable, ACID-compliant graph database designed with a high-performance distributed cluster architecture, available in self-hosted and cloud offerings

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Graph DBMS

Relational DBMS

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

Score	11.01
Rank	#47	Overall
	#8	Document stores

Score	49.70
Rank	#22	Overall
	#1	Graph DBMS

Score	124.58
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/firestore

neo4j.com

www.sqlite.org

Technical documentation

firebase.google.com/docs/firestore

neo4j.com/docs

www.sqlite.org/docs.html

Developer

Google

Neo4j, Inc.

Dwayne Richard Hipp

Initial release

2017

2007

2000

Current release

5.14, November 2023

3.44.0 (1 November 2023), November 2023

License

Commercial or Open Source

commercial

Open Source

GPL version3, commercial licenses available

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.

Neo4j Aura: Neo4j’s fully managed cloud service: The zero-admin, always-on graph database for cloud developers.

Implementation language

Java, Scala

Server operating systems

hosted

Linux

Can also be used server-less as embedded Java database.
OS X
Solaris
Windows

server-less

Data scheme

schema-free

schema-free and schema-optional

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.

Secondary indexes

yes

pluggable indexing subsystem, by default Apache Lucene

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

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
Clojure
Elixir
Go
Groovy
Haskell
Java
JavaScript
Perl
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

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

User defined Procedures and Functions

Triggers

yes, with Cloud Functions

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes using Neo4j Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Causal Clustering using Raft protocol

available in in Enterprise Version only

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

Causal and Eventual Consistency configurable in Causal Cluster setup
Immediate Consistency in stand-alone mode

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

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.

Users, roles and permissions. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

More information provided by the system vendor

Specific characteristics

Neo4j delivers graph technology that has been battle tested for performance and scale...
» more

Competitive advantages

Neo4j is the market leader, graph database category creator, and the most widely...
» more

Typical application scenarios

Real-Time Recommendations Master Data Management Identity and Access Management Network...
» more

Key customers

Over 800 commercial customers and over 4300 startups use Neo4j. Flagship customers...
» more

Market metrics

Neo4j boasts the world's largest graph database ecosystem with more than 140 million...
» more

Licensing and pricing models

GPL v3 license that can be used all the places where you might use MySQL. Neo4j Commercial...
» more

News

Top 10 Sessions From NODES 2023
28 November 2023

This Week in Neo4j: Py2Neo, Time Series, Data Clusters, Graph Database Internals and more
25 November 2023

AWS and Neo4j Join Forces to Solve LLM Hallucinations and Evolve GenAI
21 November 2023

This Week in Neo4j: RAG, Constraints, NODES 2023 Recap, CI/CD Pipeline Security and more
18 November 2023

This Week in Neo4j: Vector Index, Embeddings, Geospatial, Document QA and more
4 November 2023

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.