ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #faunadb
Symptom A client cannot establish a TLS connection to a FaunaDB instance accessed via a custom domain. The connection attempt terminates with a DNS resolution error (“Name or service not known”) before any TLS handshake occurs. Goal Determine whether the failure stems from an incorrect or missing DNS A record, an overly restrictive CAA record, or a certifica
Designing a multi-region read path that invokes server-side User Defined Functions through a client driver requires clarity on where consistency is enforced. FaunaDB provides a distributed transactional model with strict serializability and exposes FQL via a REST-based API that language SDKs abstract. UDFs encapsulate logic on the server side, while the docu
Goal I want to use FaunaDB Eventhooks to push alerts to an external endpoint only when a document change meets specific criteria, so routine writes do not trigger notification noise. The filtering logic would live inside the Eventhook function itself. Constraints and uncertainty Because Eventhooks execute within the transaction, a failed or slow external cal
Current behavior shows that a pagination cursor returned by a Paginate call is tied to the exact sort order defined in the query. When the sort order is modified—such as changing the field or direction—the previously returned 'after' cursor no longer points to a valid position in the new ordering, causing subsequent page requests to fail or return incomplete
Client-Side Resource Management Fauna drivers wrap an HTTP client to communicate with the database endpoint. To optimize performance and avoid socket exhaustion, the documented best practice is to instantiate a single, long-lived client and reuse it across the application lifecycle rather than creating a new client per request. Concurrency and Socket Exhaust
Security Model Transition FaunaDB has evolved its security architecture from legacy Secret keys toward a more granular Role-Based Access Control (RBAC) system. While the current model adheres to a deny-by-default principle, managing access for large-scale schemas requires a precise mapping of tokens to specific roles to prevent accidental public exposure. Pe
Fauna Schema Language (FSL) migrations are documented as forward-only operations. When a migration includes destructive changes such as field removal or type coercion, the forward step can discard data that a later reverse migration cannot reconstruct. Temporal document snapshots retain previous document versions for the configured retention window, yet they
We are evaluating a zero-downtime schema migration for a small FaunaDB application that depends on an index covering a field we need to rename. FaunaDB’s schema API documents additive changes as safe to apply without downtime, and breaking changes such as field renames are expected to follow a two-phase rollout where old and new fields coexist temporarily. T
When designing for high-concurrency environments in FaunaDB, the deterministic ordering system based on the Calvin protocol ensures strict serializability. However, the coordination phase of the global transaction log can introduce latency variance depending on how requests are structured. There is a design trade-off between consolidating logic into a single