Optimizing Firestore Data Structure to Reduce Read counts

[2004yash]

Currently, each member's record is stored in an individual document within the Firestore collection. While this structure allows for easy querying of individual records, it leads to a significant spike in the number of reads. This is especially problematic when performing operations that require fetching data for all members, as it results in a separate read for each document.

The same issue exists for other collections where individual records are stored as separate documents.

Proposed Solution

To optimize Firestore's read costs and improve efficiency, we propose restructuring the data:

1. Store all member records as an array within a single document.
2. Apply this restructuring to other collections with similar issues.
3. Implement pagination and partial document fetching (using Firestore's array-contains or similar features) to prevent fetching unnecessarily large data.

This approach will drastically reduce the number of reads, especially for bulk operations, while maintaining a manageable structure for the data.

[govindup63]

can you assign this issue to me