[HN Gopher] Reverse Proxy Deep Dive: Why Load Balancing at Scale...
       ___________________________________________________________________
        
       Reverse Proxy Deep Dive: Why Load Balancing at Scale Is Hard
        
       Author : miggy
       Score  : 40 points
       Date   : 2025-08-11 14:05 UTC (3 days ago)
        
 (HTM) web link (startwithawhy.com)
 (TXT) w3m dump (startwithawhy.com)
        
       | betaby wrote:
       | On the subject I can recommend the original paper from Google
       | about Maglev
       | https://static.googleusercontent.com/media/research.google.c...
       | 
       | and subsequent enhancement from Yandex folks
       | https://github.com/kndrvt/mhs
       | 
       | Explanation is at
       | https://habr.com/ru/companies/yandex/articles/858662/ use your
       | favorite translate site.
        
       | nimbius wrote:
       | its honestly not, but younger developers can be forgiven for
       | assuming traefik is all you need. the learn-to-code camps really
       | did a number on kids these days :(
       | 
       | use DSR and 50% of your traffic is taken care of.
       | https://www.loadbalancer.org/blog/direct-server-return-is-si...
       | 
       | explore load balancing lower in the stack based on ASN to
       | preroute stuff for divide and conquer. (geolocated, etc...)
       | 
       | weighted load balancing only works for uniform traffic sources.
       | youll need to weight connections based on priority or location,
       | backend heavy transactions (checkout vs just browsing the store)
       | and other conditions that can change the affinity of your user
       | (sometimes dynamically.) keepalived isnt mentioned once, or .1q
       | trunk optimization, or SRV records and failover/HA thats
       | performed in most modern browsers based on DNS information
       | itself.
        
       ___________________________________________________________________
       (page generated 2025-08-14 23:00 UTC)