> To be complete, the discussion should include optimization of interactions with the load balancer, e.g. where to terminate https, etc. Not necessarily. There

> To be complete, the discussion should include optimization of interactions with the load balancer, e.g. where to terminate https, etc. Not necessarily. There are other ways of spreading traffic, like DNS round robin for example, using the DNS delegation trick or even have client-side load balancing (which is perfectly feasible if you control the client, like your own app for example). The article itself mentions that what they're talking about is the Dropbox Edge network, an nginx proxy tier, which sounds like load balancers to me.