DBMS > Google BigQuery vs. Google Cloud Firestore vs. Oracle vs. YottaDB

System Properties Comparison Google BigQuery vs. Google Cloud Firestore vs. Oracle vs. YottaDB

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.

Widely used RDBMS

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Relational DBMS

using the Octo plugin

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

cloud.google.com/bigquery

firebase.google.com/products/firestore

www.oracle.com/database

yottadb.com

Technical documentation

cloud.google.com/bigquery/docs

firebase.google.com/docs/firestore

docs.oracle.com/en/database

yottadb.com/resources/documentation

Developer

Google

Oracle

YottaDB, LLC

Initial release

2010

2017

1980

2001

Current release

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL 3.0

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

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

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

with proprietary extensions

by using the Octo plugin

APIs and other access methods

RESTful HTTP/JSON API

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, Firebase Rules & Cloud Functions

PL/SQL

also stored procedures in Java possible

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

can be realized in PL/SQL

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

isolation level can be parameterized

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

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.

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.