DBMS > Google Cloud Firestore vs. LeanXcale vs. MySQL vs. openGauss

System Properties Comparison Google Cloud Firestore vs. LeanXcale vs. MySQL vs. openGauss

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.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Widely used open source RDBMS

An enterprise-class RDBMS compatible with high-performance, high-availability and high-performance originally developed by Huawei

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	0.28
Rank	#286	Overall
	#41	Key-value stores
	#130	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.11
Rank	#175	Overall
	#79	Relational DBMS

Website

firebase.google.com/products/firestore

www.leanxcale.com

www.mysql.com

gitee.com/opengauss
opengauss.org

Technical documentation

firebase.google.com/docs/firestore

dev.mysql.com/doc

docs.opengauss.org/en
gitee.com/opengauss/docs

Developer

Google

LeanXcale

Oracle

since 2010, originally MySQL AB, then Sun

Huawei and openGauss community

Initial release

2017

2015

1995

2019

Current release

9.0.0, July 2024

3.0, March 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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 and C++

C, C++, Java

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

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

SQL

Support of SQL

yes

through Apache Derby

yes

with proprietary extensions

ANSI SQL 2011

APIs and other access methods

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

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

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

C
Java
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

proprietary syntax

yes

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by range, list and hash)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica replication

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

not for MyISAM storage engine

yes

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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 with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

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.