Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(scaling): state the per-event lookup cost of WebSocket fan-out

Yudhi Armyndharisd60f220fdbfd
diff --git a/docs/13-horizontal-scaling.md b/docs/13-horizontal-scaling.md
index da37a861f..396dd7365 100644
--- a/docs/13-horizontal-scaling.md
+++ b/docs/13-horizontal-scaling.md
@@ -145,7 +145,9 @@
> connected to node A receives an event raised on node B. Scope honestly: this distributes event
> **fan-out only**. The per-key WS rate-limit buckets (counted per replica) and the engine registry
> are still process-local. Without `REDIS_ENABLED` the adapter is inert and delivery is single-node,
-> exactly as before.
+> exactly as before. With it, every chat event also costs the emitting node one or two `lid_mappings`
+> lookups, even when no chat-restricted key exists: it cannot know whether another replica holds a
+> restricted socket, so it names the chat in every form for the rooms to match.
>
> **Mid-connection key eviction converges on a timer, not a broadcast, and only on one node.** The
> node that processes a revoke, delete, or narrowing tears down that key's sockets synchronously, in