KMKrishnam Murarkainedilec-engineering.hashnode.dev·3d ago · 4 min readWe Killed 400 Clients' 5-Second Polling Loop and Cut Server Load by 90%Originally published on the Edilec blog: dev.to/krishnamm/we-killed-400-clients-5-second-polling-loop-and-cut-server-load-by-90-1fdf Our status dashboard feature started life as the simplest thing tha00
KMKrishnam Murarkainedilec-engineering.hashnode.dev·Jul 31 · 5 min readAutomated Deploy Pipelines: Cutting Release Time From Three Days to Forty MinutesOriginally published on the Edilec blog. For the first year of Edilec, shipping a release meant blocking out an afternoon and hoping nothing else came up. A deploy was: SSH into the box, git pull, sto00
KMKrishnam Murarkainedilec-engineering.hashnode.dev·Jul 29 · 4 min readA Dependency That's Slow Is Worse Than One That's Down: What Building Circuit Breakers Taught UsWe used to think the worst failure mode for a downstream service was an outage. It isn't. An outage is clean — the connection refuses, the request fails fast, your code hits a catch block and moves on00
KMKrishnam Murarkainedilec-engineering.hashnode.dev·Jul 28 · 4 min readHow Routing Reads to Replicas Took Our Primary From 90% CPU to 20%For most of a year, every query our application made — reads and writes alike — went to the same primary Postgres instance. It worked fine until it didn't: our primary was sitting at a sustained 85-9000
KMKrishnam Murarkainedilec-engineering.hashnode.dev·Jul 28 · 5 min readThe 40x Traffic Spike From One Partner: What Token-Bucket Rate Limiting Actually Buys YouOne of our integration partners pushed a firmware update to their fleet of devices, and every device in that fleet decided to sync at once. Our API request volume from that single partner went from ro00
