Cloud Firestore for Users who are new to Firestore
Jul 14, 2021
auto_awesome
Allison Kornher, a Cloud Technical Resident at Google, introduces us to Firestore, a scalable NoSQL document database. She explains the differences between SQL and NoSQL databases and the four categories of NoSQL databases. Each Firestore document belongs to a collection and is stored in key value pairs for easy management. Subcollections add to the flexibility of Firestore design. Allison gives tips for getting started with Firestore and recommends considering the CAP theorem when choosing a database type.
Firestore is a flexible NoSQL document database, allowing easy data organization and changes.
Choosing a database type depends on the situation and understanding the CAP theorem is crucial.
Deep dives
Firestore Overview and Structure
Firestore is a document database integrated with Firebase, allowing scalable data storage. Collections organize data, with documents storing specific info like a pizza order. Firestore's flexibility accommodates changing data requirements, unlike traditional SQL databases.
Sharing Persistent Disk Across VMs
Previously read-only, persistent disks in Google Cloud can now be mounted with multiple writers, enabling simultaneous reading and writing from various machines. While suitable for numerous use cases like shared rendering or transcoding tasks, certain file systems compatibility is essential for proper functioning.
Alternative Solutions to Disk Sharing
Apart from shared persistent disks, other options like Google Cloud Storage, NFS protocol via Cloud Filestore, hosted databases like Firestore, and custom application databases provide scalable file sharing solutions. Choose based on application needs and integration requirements for optimal performance.
Setting Up Persistent Disk Connections
Persistent disks across VMs are connected using simple commands via APIs, G Cloud, or the console. Attaching disks to VMs at start-up or during runtime is seamless, enhancing connectivity and data sharing capabilities among multiple instances.
Brian Dorsey and Mark Mirchandani are talking intro to Firestore this week with fellow Googler Allison Kornher. Allison, a Cloud Technical Resident, starts the show telling us about the program and how it brought her to Firestore.
Allison takes us through the differences between SQL and NoSQL databases and describes the four categories of NoSQL databases: family, document, key value, and graph. Firestore is a scalable, flexible NoSQL document database. To illustrate the uses and benefits of Firestore, Allison walks us through a delicious pizza example. Each document in the database belongs to a collection, which is used to organize these documents. Firestore documents are assigned an identifier and can be quickly changed and called within their collections. Because these documents are stored in an implicit schema in key value pairs, developers have control over the details of database organization and data change and growth are easy to manage. The availability of subcollections further adds to the flexibility of Firestore database design.
Choosing a database type will depend on the situation, and Allison suggests this starts with a look at CAP theorem. If a document database is your database of choice, Allison gives our listeners tips for getting started with Firestore and clearing any hurdles along the way.
Allison Kornher
Allison is a Cloud Technical Resident and has worked helping startups looking to join GCP and in the Premium Tier Cloud Support organization with a focus on Storage.
Cool things of the week
BigQuery admin reference guide: Tables & routines blog