firebase-operations

Batch writes bundle up to 500 operations atomically using the admin SDK's batch API. Create a batch instance, chain set, update, or delete operations on documents across collections, then commit. All operations succeed or fail together, ensuring data consistency without manual transaction management.

Use Timestamp.now() from the admin SDK to capture server time when writing documents. Convert timestamps to ISO strings for API responses. The admin SDK automatically serializes and deserializes timestamps, preserving precision across document reads and writes in collections like projects and users.

Transactions ensure atomicity across multiple documents using the admin SDK's transaction API. Read documents, apply conditional logic, then write changes—all succeed or retry together if conflicts occur. This pattern prevents race conditions when updating related data across collections.

Yes, the admin SDK supports querying, creating, updating, and deleting documents across nested and root-level collections. Reference documents by path, apply filters and pagination, and execute operations on comments, whispers, ai_usage, and other collections with the same CRUD patterns.

Use limit and offset or cursor-based pagination with the admin SDK. Fetch documents in chunks, store the last document as a cursor, and use startAfter() for the next page. This pattern scales efficiently for collections like projects and users without loading entire result sets.

Batch writes support up to 500 operations per batch. Each operation counts as one, whether it's a set, update, or delete. For larger workloads, split into multiple batches or use transactions for strongly consistent updates across smaller operation sets.