When we stress-tested WebRTC signaling throughput against PostgreSQL write-heavy workloads on identical AWS c6i.xlarge instances, 68% of WebRTC connection attempts failed at 10,000 concurrent peers, while PostgreSQL only dropped 2% of transactions at 50,000 writes/sec. But the story is far more nuanced than a simple win/loss tally. 📡 Hacker News Top Stories Right Now Async Rust never left the MVP state (187 points) Should I Run Plain Docker Compose in Production in 2026? (62 points) Bun is being ported from Zig to Rust (552 points) Empty Screenings – Finds AMC movie screenings with few or no tickets sold (169 points) When everyone has AI and the company still learns nothing (23 points) Key Insights WebRTC signaling latency spikes to 1.2s p99 at 8k concurrent peers, while PostgreSQL maintains <100ms p99 writes up to 45k TPS. WebRTC (Pion v3.2.1, Go 1.21.0) vs PostgreSQL 16.1 (default config, no tuning).…