In 15 years of backend engineering, I’ve never seen two technologies as misunderstood as PostgreSQL’s internal query execution and HTTP/3’s transport layer—until we benchmarked them against each other with 1.2M requests per second workloads, the gap between their performance ceilings shocked even our most senior contributors. 📡 Hacker News Top Stories Right Now .de TLD offline due to DNSSEC? (536 points) Accelerating Gemma 4: faster inference with multi-token prediction drafters (455 points) Computer Use is 45x more expensive than structured APIs (322 points) Three Inverse Laws of AI (367 points) Write some software, give it away for free (137 points) Key Insights PostgreSQL 16’s parallel sequential scan delivers 427K rows/sec on 8 vCPU instances, 3.1x faster than HTTP/3’s QUIC stream multiplexing for stateful workloads. HTTP/3’s 0-RTT handshake reduces connection latency by 82% compared to PostgreSQL’s default TCP keepalive for stateless API calls.…