Choose a data structure

Remember, when you structure your data in Cloud Firestore, you have a few different options:

Consider the advantages of each option as they relate to your use case. A few example structures for hierarchical data are outlined in this guide.

You can nest complex objects like arrays or maps within documents.

Advantages: If you have simple, fixed lists of data that you want to keep within your documents, this is easy to set up and streamlines your data structure.
Limitations: This isn't as scalable as other options, especially if your data expands over time. With larger or growing lists, the document also grows, which can lead to slower document retrieval times.
What's a possible use case? In a chat app, for example, you might store a user's 3 most recently visited chat rooms as a nested list in their profile.

You can create collections within documents when you have data that might expand over time.

Advantages: As your lists grow, the size of the parent document doesn't change. You also get full query capabilities on subcollections.
Limitations: You can't easily delete subcollections.
What's a possible use case? In the same chat app, for example, you might create collections of users or messages within chat room documents.

Create collections at the root level of your database to organize disparate data sets.

Advantages: Root-level collections offer the most flexibility and scalability, along with powerful querying within each collection.
Limitations: Getting data that is naturally hierarchical might become increasingly complex as your database grows.
What's a possible use case? In the same chat app, for example, you might create one collection for users and another for rooms and messages.