Node.js API Boundaries for Realtime Quota Protection in Live Auction Dashboards

Short answer: put a small, explicit quota boundary in front of every realtime connection, make reconnect and backfill consume a separate budget, and measure freshness rather than WebSocket count. For a live auction dashboard, this keeps a reconnect storm from starving the bids, typing indicators, and read receipts that operators actually need. The page that wakes the on-call engineer is usually not the page they needed. It says realtime_connections > 50,000 or reports a spike of HTTP 429 responses. Meanwhile the auction view is quietly showing old bids because clients are retrying history reads and consuming the same API quota as the live stream. The first fix is to name the traffic classes: live fan-out, presence and typing signals, receipts, and backfill are different workloads with different loss tolerance. The alert is late: trace the quota failure backward Imagine a regional network flap drops 18% of browser connections in two minutes. Every tab reconnects with exponential backoff, then asks for the last 500 events. The backfill requests arrive together, compete with bid updates, and inflate p95 latency. A connection-count alert fires after the damage is visible, while the useful early signal was the ratio of reconnect attempts to successful session resumes. That sequence deserves a trace of its own. At 12:00:00, a viewer has acknowledged event 8,421. At 12:00:02, the socket closes and the browser schedules a resume. At 12:00:03, the resume is admitted, but the client also starts a second history request because its UI timer has not heard from the first one. At 12:00:04, both requests pass a connection-only limiter and read the same rows. At 12:00:05, a bid arrives behind those reads, so the dashboard is connected yet stale. A class-aware boundary would admit the resume, reject the duplicate backfill with Retry-After: 2 , and leave the bid lane untouched. The important detail is not the exact timestamps; it is that each transition is visible and attributable, s