DBMS > Google Cloud Firestore vs. Microsoft Access vs. Sequoiadb vs. Snowflake

System Properties Comparison Google Cloud Firestore vs. Microsoft Access vs. Sequoiadb vs. Snowflake

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.

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.)

NewSQL database with distributed OLTP and SQL

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

Primary database model

Document store

Relational DBMS

Document store
Relational DBMS

Relational 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	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

firebase.google.com/products/firestore

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

www.sequoiadb.com

www.snowflake.com

Technical documentation

firebase.google.com/docs/firestore

developer.microsoft.com/en-us/access

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

Developer

Google

Microsoft

Sequoiadb Ltd.

Snowflake Computing Inc.

Initial release

2017

1992

2013

2014

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Server: AGPL; Client: Apache V2

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

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL-like query language

yes

APIs and other access methods

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

ADO.NET
DAO
ODBC
OLE DB

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

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

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

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

since Access 2010 using the ACE-engine

JavaScript

user defined functions

Triggers

yes, with Cloud Functions

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Source-replica replication

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

but no files for transaction logging

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

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.

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

simple password-based access control

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

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.