Firestore Collections and Documents

Introduction to Firestore Collection and Document Basics

Welcome back! Previously, we explored Cloud Firestore, a flexible NoSQL database service designed for modern application development. In this session, we will focus on the essential building blocks of Firestore: collections and documents . Firestore organizes data in a hierarchical structure. At the top level, you have collections, which are containers for documents . Each document holds data as key-value pairs, and documents can themselves contain subcollections, allowing for nested data organization. Unlike traditional relational databases, Firestore does not require you to define a schema in advance — each document in a collection can have a different structure, making it easy to adapt to changing data requirements. Understanding how to structure your data using collections and documents is fundamental to building scalable and efficient applications with Firestore.

How Firestore Identifies and Organizes Documents

In Firestore, data is organized into collections and documents. A collection is a group of documents, and each document is a set of key-value pairs. Every document within a collection is uniquely identified by a document ID . Collections : Collections are containers for documents. They do not store any data themselves but serve as namespaces for grouping related documents. For example, you might have a collection called users to store user profiles. Documents : Documents are individual records within a collection. Each document has a unique ID within its collection, which can be automatically generated or specified manually. Document IDs are used to retrieve, update, or delete specific documents. For example, consider a blogPosts collection where each document represents a blog post. Each document might have fields such as author, date, and title : Document ID author date title post1 A1 2020-01-01 New Year Reflections post2 A1 2020-01-02 Another Day in Life Firestore ensures that each document within a collection has a unique ID but does not enforce uniqueness or structure across different collections or subcollections. This flexible approach allows you to organize your data in a way that best fits your application's needs.

Document ID	author	date	title
post1	A1	2020-01-01	New Year Reflections
post2	A1	2020-01-02	Another Day in Life

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal

Working with Subcollections

Documents in Firestore can contain subcollections, which are collections nested within a specific document. This hierarchical structure is useful for organizing related data. For example, a user document might have a subcollection of posts, or a blog post document might have a subcollection of comments.

Here's how to create and access subcollections:

Python

from google.cloud import firestore

# Initialize the Firestore client
db = firestore.Client()

# Create a subcollection within a document
# This creates a 'posts' subcollection within the 'user_123' document
db.collection('users').document('user_123').collection('posts').add({
    'title': 'My First Post',
    'content': 'This is the content of my first post.',
    'created_at': '2023-06-15'
})

# Add another document to the same subcollection
db.collection('users').document('user_123').collection('posts').document('post_001').set({
    'title': 'My Second Post',
    'content': 'This is my second post.',
    'created_at': '2023-06-16'
})

# List subcollections within a document
user_doc = db.collection('users').document('user_123')
subcollections = user_doc.collections()
print("Subcollections in user_123:", [subcoll.id for subcoll in subcollections])

from google.cloud import firestore

# Initialize the Firestore client
db = firestore.Client()

# Create a subcollection within a document
# This creates a 'posts' subcollection within the 'user_123' document
db.collection('users').document('user_123').collection('posts').add({
    'title': 'My First Post',
    'content': 'This is the content of my first post.',
    'created_at': '2023-06-15'
})

# Add another document to the same subcollection
db.collection('users').document('user_123').collection('posts').document('post_001').set({
    'title': 'My Second Post',
    'content': 'This is my second post.',
    'created_at': '2023-06-16'
})

# List subcollections within a document
user_doc = db.collection('users').document('user_123')
subcollections = user_doc.collections()
print("Subcollections in user_123:", [subcoll.id for subcoll in subcollections])

Output:

Subcollections in user_123: ['posts']

Subcollections in user_123: ['posts']

Subcollections are created automatically when you add the first document to them, just like top-level collections. The path structure follows the pattern: collection/document/subcollection/document, and this nesting can continue as deep as needed for your application's data model.

Introduction to Firestore Collection and Document Basics

How Firestore Identifies and Organizes Documents

Join the 1M+ learners on CodeSignal

Data Types in Firestore

Creating Collections and Documents in Firestore

Working with Subcollections

Listing Collections in Firestore

Attribute Naming Conventions

Review and Upcoming Practice Exercises