DBMS > etcd vs. Google BigQuery vs. Google Cloud Firestore vs. Microsoft Access

System Properties Comparison etcd vs. Google BigQuery vs. Google Cloud Firestore vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

Primary database model

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

etcd.io
github.com/etcd-io/etcd

cloud.google.com/bigquery

firebase.google.com/products/firestore

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

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

cloud.google.com/bigquery/docs

firebase.google.com/docs/firestore

developer.microsoft.com/en-us/access

Developer

Google

Microsoft

Initial release

2010

2017

1992

Current release

3.4, August 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

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

FreeBSD
Linux
Windows

experimental

hosted

Windows

Not a real database server, but making use of DLLs

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

gRPC
JSON over HTTP

RESTful HTTP/JSON API

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

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, Firebase Rules & Cloud Functions

yes

since Access 2010 using the ACE-engine

Triggers

yes, watching key changes

yes, with Cloud Functions

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

yes

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

In-memory capabilities

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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

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.