DBMS > Google Cloud Firestore vs. Microsoft Access vs. MySQL vs. Spark SQL vs. Splice Machine

System Properties Comparison Google Cloud Firestore vs. Microsoft Access vs. MySQL vs. Spark SQL vs. Splice Machine

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.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used open source RDBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Document store

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	7.85
Rank	#51	Overall
	#8	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

firebase.google.com/products/firestore

www.microsoft.com/en-us/microsoft-365/access

www.mysql.com

spark.apache.org/sql

splicemachine.com

Technical documentation

firebase.google.com/docs/firestore

developer.microsoft.com/en-us/access

dev.mysql.com/doc

spark.apache.org/docs/latest/sql-programming-guide.html

splicemachine.com/how-it-works

Developer

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Splice Machine

Initial release

2017

1992

1995

2014

Current release

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

3.5.0 ( 2.13), September 2023

3.1, March 2021

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

AGPL 3.0, commercial license 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Scala

Java

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
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

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

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

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

Java
Python
R
Scala

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

yes

Java

Triggers

yes, with Cloud Functions

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes, utilizing Spark Core

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Yes, via Full Spark Integration

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

but no files for transaction logging

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

but no files for transaction logging

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.

a simple user-level security was built in till version Access 2003

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.