3 ms·
There needs to be more publications covering this, because I don't see this becoming common knowledge or practiced very often. Then there's the modern design d
by 0xbadcafebee 10y ago
There needs to be more publications covering this, because I don't see this becoming common knowledge or practiced very often.
Then there's the modern design decisions that make some of these subjects taboo, like "you should never cache anything" and "a single node can handle a million concurrent connections so why worry" and "let's make all our machines use 99% of their capacity with containers because it's more efficient and hope we can deploy standbys before the database queues too much and blows the entire stack up". With the emergence of the pseudo-Devops cargo cult, people who like using JavaScript for server backend code are designing infrastructure they've never administered before. (sorry for the rant)
There was a really great paper published a few years ago that was basically an Everything You Need To Know To Run Large Scale Enterprise Systems type paper. I can never find it when these types of threads come up, but it was dozens of pages long and really in-depth.
- torinmr 10y agoThe SRE Book (http://shop.oreilly.com/product/0636920041528.do http://shop.oreilly.com/product/0636920041528.do) has a number of chapters on load balancing that are well worth reading. One thing that the book covers that I think this article glossed over was the fact that in sufficiently large systems there's never a single "load balancer" - instead there's many layers of load balancing systems at different levels of the stack. E.g.: DNS load balancing -> high capacity network-level load balancing -> shared reverse HTTP proxy -> application server -> database (with a "load balancer" internal to the application server load balancing among DB replicas).
- peterwwillis 10y agoThey mention there are different applications for load balancers, and then use one or two examples. But their main points are the most important ones: if you don't know what you're using it for, it might be worthless. The SRE book seems to only have a couple sub-chapters on it, so I would recommend looking up white papers and best practices for your particular application of load balancing. Safari Books has over 17,000 matches for "load balancing" in its library, for example, and F5 has 12 white papers on it just for their products.
- noam87 10y agoreplying just in case someone finds what paper that was.
- theptip 10y agohttp://mvdirona.com/jrh/talksAndPapers/JamesRH_Lisa.pdf http://mvdirona.com/jrh/talksAndPapers/JamesRH_Lisa.pdf ? This was featured on Adrian Colyer's blog earlier this year (https://blog.acolyer.org/2016/09/12/on-designing-and-deploying-internet-scale-services/ https://blog.acolyer.org/2016/09/12/on-designing-and-deployi...)