ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Want to guarantee that a user profile and its default settings are created together in FaunaDB? Learn how FaunaDB’s native multi‑document ACID transactions work, when to use them, and a step‑by‑step FQL example that keeps your data consistent without application‑level locks.
Fauna executes an entire FQL expression as one ACID transaction, letting you enforce multi-document invariants like balance transfers directly in the query instead of application code.
Learn how to paginate large FaunaDB result sets using the cursor‑based 'after' pattern, with step‑by‑step code, checks, and recovery guidance.
When an application consumes Fauna document streams from a serverless or edge HTTP runtime, the official driver exposes a single stream API while the platform's HTTP agent, proxy, and egress controls sit between the client and Fauna. The integration must choose a reconnect reconciliation policy: whether a resumed stream combined with a temporal snapshot read
faunadb