DBMS > Google Cloud Firestore vs. MarkLogic vs. MySQL vs. Oracle Rdb

System Properties Comparison Google Cloud Firestore vs. MarkLogic vs. MySQL vs. Oracle Rdb

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.

Operational and transactional Enterprise NoSQL database

Widely used open source RDBMS

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

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	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.04
Rank	#184	Overall
	#84	Relational DBMS

Website

firebase.google.com/products/firestore

www.progress.com/marklogic

www.mysql.com

www.oracle.com/database/technologies/related/rdb.html

Technical documentation

firebase.google.com/docs/firestore

www.progress.com/marklogic/documentation

dev.mysql.com/doc

www.oracle.com/database/technologies/related/rdb-doc.html

Developer

Google

MarkLogic Corp.

Oracle

since 2010, originally MySQL AB, then Sun

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2017

2001

1995

1984

Current release

11.0, December 2022

9.0.0, July 2024

7.4.1.1, 2021

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

C and C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

HP Open VMS

Data scheme

schema-free

Schema can be enforced

yes

Flexible Schema (defined schema, partial schema, schema free)

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

SQL92

yes

with proprietary extensions

yes

APIs and other access methods

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

via XQuery or JavaScript

yes

proprietary syntax

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

ACID

not for MyISAM storage engine

yes, on a single node

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, with Range Indexes

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.

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept

no user groups or roles

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.