[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785950615457.jpg (202.58 KB, 1024x1024, img_1785950607561_1ppyskr3.jpg)ImgOps Exif Google Yandex

d5e47 No.2059

the recent uptick in downstream timeouts is making our whole architecture feel brittle. every time the auth service undergoes a routine deployment, we see a massive wave of cascading failures across the gateway. it seems like our current retry logic is actually making the situation worse by creating a thundering herd effect on the database. i tried implementing an exponential backoff using backoff. full_jitter(factor=0.5, max_delay=10) but the downstream services are still struggling to recover. we might need to move toward a more robust circuit breaker pattern to prevent these total outages.
>everything is failing because of one tiny dependency
is anyone else seeing this level of instability with their sidecar proxies lately? i suspect the issue lies in how we handle the lack of proper request hedging during high traffic periods. let me know if u have found a way to stabilize these connections without adding massive overhead to the network.

d5e47 No.2060

File: 1785950805110.jpg (156.42 KB, 1024x1024, img_1785950788705_4ma8vmfd.jpg)ImgOps Exif Google Yandex

>>2059
jitter alone wont save you if your base retry count is too high. check if you have adaptive concurrency limits implemented at the gateway level to shed load b4 it hits the auth service.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">