Live data from Hacker News

Viewing profile — singhsanjay12

singhsanjay12

HN member
Joined
Sun, Aug 03, 2025, 11:23 PM UTC
HN karma
24
Public activity
21 items

About singhsanjay12

hello@singh-sanjay.com

software engineer: working on edge/traffic, service discovery, load balancing, kubernetes

meet.hn/city/37.3893889,-122.0832101/Mountain-View

Recent public activity

  1. comment
    Comment #49207162

    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 earli…

  2. comment
    Comment #49207140

    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 earl…

  3. story
  4. comment
    Comment #48754400

    [flagged]

  5. story
  6. comment
    Comment #47342747

    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 arr…

  7. story
  8. comment
    Comment #47226525

    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 behavio…

  9. comment
  10. comment
    Comment #47226237

    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 th…

  11. comment
    Comment #47226102

    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 …

  12. story
  13. comment
    Comment #47185468

    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…

  14. story
  15. comment
    Comment #47133930

    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 example…

  16. comment
    Comment #47133883

    > 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 cr…

  17. comment
    Comment #47133506

    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 im…

  18. comment
    Comment #47133161

    Ok, do you mind briefly describing, what issues you saw on mobile?

  19. comment
    Comment #47133151

    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 standardiz…

  20. comment
    Comment #47130432

    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…

  21. story