Mr Vitaligator
Mr Vitaligator @JumpingVPN ·
Most systems reconnect. This one doesn’t lose the session. Transport changes. Attacks get rejected. Behavior gets proven. This is not “it works”. This is: provable continuity under failure. #networking #infosec #distributed
4
Prathamesh
Prathamesh @pratham2812 ·
Replying to @pratham2812
Put together a small Go library exploring this: github.com/bhope/hedge Inspired by Google’s “Tail at Scale” Would love to get your feedback on the tool. Also curious how others approach tail latency? #golang #distributed
GitHub - bhope/hedge: Adaptive hedged requests for Go. Cut your p99 latency with zero configurati...

Adaptive hedged requests for Go. Cut your p99 latency with zero configuration. Based on Google's "The Tail at Scale" paper. - bhope/hedge

From github.com
22
Dinakaran
Dinakaran @DinakaranNews ·
வீடு வீடாக பாத்திரம் வினியோகித்த தவெகவினர்: திருச்செங்கோடு அருகே பரபரப்பு dinakaran.com/news/monks-dis… #monks #distributed #TVK #DinakaranNews
வீடு வீடாக பாத்திரம் வினியோகித்த தவெகவினர்: திருச்செங்கோடு அருகே பரபரப்பு - Dinakaran - Dinakaran

வீடு வீடாக, பாத்திரம், வினியோகித்த, தவெகவினர்

From dinakaran.com
1
368
vigneshbalaji.dev
vigneshbalaji.dev @vigneshbaladev ·
In a monolithic application, tracking a request is easy because everything happens in one place. But in a microservice architecture, a single click (like "Place Order") might trigger a dozen different services: auth, inventory, payment, shipping, and email. #Distributed
1
23