How We Replaced Apache with Nginx 1.25 and Cut Reverse Proxy Latency by 25% for Our APIs
For 18 months, our API gateway’s p99 reverse proxy latency hovered at 210ms, costing us $18k/month in wasted compute and driving a 12% churn rate among high-frequency API consumers. We replaced Apache 2.4.57 with Nginx 1.25.3, and cut that latency by 25% to 157ms, with zero unplanned downtime. Here’s exactly how we did it, with benchmarks, code, and real production numbers. 📡 Hacker News Top Stories Right Now Ghostty is leaving GitHub (1639 points) ChatGPT serves ads. Here's the full attributio
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3900225) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ANKUSH CHOUDHARY JOHAL Posted on Apr 29 • Originally published at johal.in How We Replaced Apache with Nginx 1.25 and Cut Reverse Proxy Latency by 25% for Our APIs #replaced #apache #nginx #reverse For 18 months, our API gateway’s p99 reverse proxy latency hovered at 210ms, costing us $18k/month in wasted compute and driving a 12% churn rate among high-frequency API consumers.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
