singhsanjay12

5 ms·

1.
by singhsanjay12 1mo ago
We explored a closely related architecture at LinkedIn around centralized identity and policy enforcement at the action/resource boundary, which I presented at RSA Conference earlier this year in San Francisco. Interesting to see simil
2.
by singhsanjay12 1mo ago
We explored a closely related architecture at LinkedIn around centralized identity and policy enforcement at the action/resource boundary, which we presented at RSA Conference earlier this year. The extension to AI agents and machine-s
3.
Never Liked the Tesla Handles(techcrunch.com)
3 points by singhsanjay12 2mo ago|0 comments
4.
How reverse proxies handle concurrent requests at scale (ATS, HAProxy, Envoy)(singh-sanjay.com)
6 points by singhsanjay12 6mo ago|1 comments
5.
by singhsanjay12 6mo ago
I wrote a deep dive on how modern reverse proxies handle thousands of concurrent requests. The article walks through what actually happens inside a proxy when multiple requests arrive at the same time: connection handling, request queues, e
6.
by singhsanjay12 7mo ago
This matches what I've seen too. Resolver-level resilience is often manageable centrally. The harder part is application-level recovery; especially in larger orgs where DNS behavior spans multiple teams. Even with low TTLs or cache flu
7.
by singhsanjay12 7mo ago
fixed it
8.
by singhsanjay12 7mo ago
Nice. Running Unbound locally with intelligent upstream selection and caching definitely reduces blast radius from edge resolver outages. I haven't tried Unbound but I’m curious though, how do you handle recovery behavior when the fail
9.
Recovering from DNS Outages in Distributed Systems(singh-sanjay.com)
3 points by singhsanjay12 7mo ago|6 comments
10.
by singhsanjay12 7mo ago
DNS keeps showing up in outage postmortems, but what's often missing is discussion about recovery, not just prevention. In this post, I break down common DNS failure patterns (TTL propagation, resolver overload, control plane dependenc
11.
When to Use DNS Load Balancing (and When Not To)(singh-sanjay.com)
2 points by singhsanjay12 7mo ago|1 comments
12.
by singhsanjay12 7mo ago
This isn't a critique of DNS load balancing. DNS works well in certain scenarios (multi-region failover, coarse traffic steering), but I've seen it misapplied in cases where faster failure detection or finer-grained routing was re
13.
by singhsanjay12 7mo ago
For client-side LB, moving active healthcheck outside into dedicated service, wouldn't it create more reliability issues with one more service to worry about? Are there any examples of this approach being used in the industry?
14.
by singhsanjay12 7mo ago
> when a single endpoint in a service begins having high latency Yes, have seen this first hand. Tracking the latency per endpoint in a sliding window helped in some way, but it created other problems for low qps services.
15.
by singhsanjay12 7mo ago
Agree - sliding window error rates plus client-side circuit breakers (with half-open probes and ramp-up) work really well in practice, and the recovery-speed point is especially important. The only nuance I was trying to call out is what ha
16.
by singhsanjay12 7mo ago
Ok, do you mind briefly describing, what issues you saw on mobile?
17.
by singhsanjay12 7mo ago
The idea is attractive (especially for draining), but once you try to map arbitrary inbound client connections onto backend-initiated "reverse" pipes, you end up needing standardized semantics for multiplexing, backpressure, failu
18.
Why Your Load Balancer Still Sends Traffic to Dead Backends(singh-sanjay.com)
47 points by singhsanjay12 7mo ago|28 comments
19.
by singhsanjay12 7mo ago
I wrote this after seeing cases where instances were technically “up” but clearly not serving traffic correctly. The article explores how client-side and server-side load balancing differ in failure detection speed, consistency, and operati