3 ms·
> "some of the commenters dismissed either it ("impossible") or me ("doesn't know anything about load balancing"). " This to me is odd. Was this posted when AW
by KaiserPro 9y ago
> "some of the commenters dismissed either it ("impossible") or me ("doesn't know anything about load balancing"). "
This to me is odd. Was this posted when AWS's ELBs were new and shiny?
Most of the big failure cases I've dealt with are along these lines.
One server does something stupid and gobbles up the world.
That being said, this is a very neat way of describing the problem, I shall be referencing this in the future, I might start putting that in an interview question....
- AdmiralAsshat 9y agoGiven the author's presumed gender, I understood it to be thinly-veiled sexism. But I could be wrong.
- KaiserPro 9y agoPerhaps, or just typical dickishness. (mind you its the same thing really.) As a devop I get told or sorts of "facts" about various building blocks. We are currently looking at low latency API (read not using HTTP) half of the suggestions I got back were about using haskell or Go. No one bothered with the low hanging fruit, like re-using TCP sockets, using predefined schemas instead of json, etc etc. Not one person thought about LB latency...