DBMS > Google Cloud Firestore vs. Neo4j vs. Snowflake vs. Tarantool vs. TerarkDB

System Properties Comparison Google Cloud Firestore vs. Neo4j vs. Snowflake vs. Tarantool vs. TerarkDB

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

Cloud-based data warehousing service for structured and semi-structured data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Graph DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	44.89
Rank	#21	Overall
	#1	Graph DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

firebase.google.com/products/firestore

neo4j.com

www.snowflake.com

www.tarantool.io

github.com/bytedance/terarkdb

Technical documentation

firebase.google.com/docs/firestore

neo4j.com/docs

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Neo4j, Inc.

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2017

2007

2014

2008

2016

Current release

5.20, May 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

GPL version3, commercial licenses available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

restricted open source version 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.

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

Implementation language

Java, Scala

C and C++

C++

Server operating systems

hosted

Linux

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

hosted

BSD
Linux
macOS

Data scheme

schema-free

schema-free and schema-optional

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

pluggable indexing subsystem, by default Apache Lucene

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

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

CLI Client
JDBC
ODBC

Open binary protocol

C++ API
Java API

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

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C++
Java

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

User defined Procedures and Functions

user defined functions

Lua, C and SQL stored procedures

Triggers

yes, with Cloud Functions

yes

via event handler

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes using Neo4j Fabric

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

yes

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

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)

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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

This Week in Neo4j: GraphAcademy, Knowledge Graph, Predictions, GraphRAG and more
22 June 2024

This Week in Neo4j: Llamaindex, Semantic Search, Graph Database, Entity Resolution and more
15 June 2024

Neo4j-Databricks Connector Delivers Deeper Insights, Faster GenAI Development
10 June 2024

This Week in Neo4j: Podcast, Testing, Knowledge Graph, GenAI and more
8 June 2024

Neo4j and Snowflake Bring Graph Data Science Into the AI Data Cloud
4 June 2024

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.