ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Problem Overview When a custom domain is configured for Appwrite’s Realtime service, the client first performs a DNS lookup, then establishes a TLS handshake. A timeout before the handshake indicates a potential DNS or certificate issue. Goal & Constraints The objective is to determine whether the failure originates from DNS propagation (missing A record
PostgreSQL Logical Replication and Storage Supabase Realtime leverages the supabase_realtime publication and logical replication slots to stream database changes to clients via WebSockets. This architecture relies on the PostgreSQL Write Ahead Log (WAL) to track and broadcast INSERT , UPDATE , and DELETE events. Resource Constraints In environments with high
Goal Bound a large Firestore collection in a Flutter app and page through it using limit() with startAfterDocument() , while keeping a real-time listener active on the initial page. Constraints Firestore pagination requires a deterministic ordering field backed by a matching index, and startAfterDocument() depends on that order staying identical between page
Determine whether enabling Photon’s Async HTTP fallback or adjusting the server’s MaxCCU setting deterministically reduces the latency spikes observed when many clients issue OpCreateRoom or OpJoinRoom operations concurrently. Photon Realtime queues these operations on the game server’s per‑peer message dispatch queue, and the latency increase depends on an
Goal: Determine whether the increase in broadcast latency observed in Supabase Realtime is caused by connection‑pool exhaustion, PgBouncer backpressure, or Node.js event‑loop lag when many clients open WebSocket connections simultaneously. Constraints: The threshold at which latency becomes noticeable is unknown and may differ between free and paid project t
supabase
flutter
photonengine