PostgreSQL Connection Pool Exhaustion
It's 14:30 on Black Friday. Your monitoring alerts fire: response times have spiked.
5 интерактивных · 11 кейсов всего · Обновляется еженедельно
It's 14:30 on Black Friday. Your monitoring alerts fire: response times have spiked.
Your analytics API handles 200 RPS flawlessly in staging.
Your team deployed a new feature yesterday. Today the SRE reports one backend node is running at 94% CPU while the other four are nearly idle.
The daily financial report job has always run at 03:00 UTC and finished in under 1 minute.
The booking API handles steady-state load (150 RPS) perfectly — P95 under 120ms.
Two services write to the same tables in opposite order. Transactions lock each other indefinitely.
Read replica falls 45 minutes behind primary. Read queries returning stale data.
Random 8-12 second latency spikes with no CPU or memory pressure. GC logs hold the answer.
Write throughput drops 70% under load. iostat shows 100% disk utilization.
Team receives 200+ alerts per day. On-call engineers start ignoring them.
Internal API calls adding 200ms overhead. External latency is fine. Network path issue.
🚧 Новые кейсы добавляются каждую неделю · Подпишитесь