When is a transaction better than a batched write in Firestore?

Use transactions when a write operation depends on the current state of a document (read-modify-write). Use batched writes for performance when you need to update multiple documents atomically without reading them first.

Does this skill provide guidance on composite indexes?

Yes, it includes patterns for identifying when composite indexes are required and provides the JSON structure for firestore.indexes.json to support complex filtering and sorting.

How does this skill help with Firestore's 1MB document limit?

The skill provides patterns for referencing and subcollections to avoid embedding large arrays or frequently growing data sets that would eventually exceed the 1MB per-document limit.

When should I use a subcollection instead of a root collection?

Use subcollections for data tightly coupled to a parent document that doesn't require global querying. Use root collections for many-to-many relationships and data that needs to be queried across the entire database.

Firestore Data Modeling Patterns

Name: Firestore Data Modeling Patterns
Author: Agentient

byAgentient

0•

Database Management

Provides expert guidance on structuring Firestore NoSQL databases for optimal performance, scalability, and cost-efficiency.

The Firestore Data Modeling Patterns skill equips developers with standardized architectural patterns for NoSQL database design within the Firebase ecosystem. It offers deep insights into critical architectural decisions, such as choosing between subcollections and root collections, managing complex many-to-many relationships, and implementing atomic operations using transactions or batches. By applying these battle-tested patterns, developers can avoid common pitfalls like the 1MB document limit, ensure efficient query performance through proper indexing, and maintain predictable data lifecycles in production-grade applications.

Key Features

01Optimization patterns for composite indexes and collection group queries

020 GitHub stars

03Architectural guidance for subcollection vs. root collection hierarchies

04Implementation templates for atomic transactions and high-performance batched writes

05Strategies for data embedding and referencing based on relationship types

06Best practices for managing document size limits and data denormalization

Use Cases

01Implementing complex data relationships and atomic updates in Firebase projects

02Designing a scalable database schema for a multi-tenant SaaS application

03Optimizing Firestore query performance to reduce read/write latency and costs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add agentient/vibekit firestore-data-modeling-patterns

For use in Claude.ai and ChatGPT

Download Skill