3 ms·
This response is exactly why I posted on HN! Love this site. In terms of active-active, I guess I need two physically disparate load balancers that heart beat
by dabeeeenster 18y ago
This response is exactly why I posted on HN! Love this site.
In terms of active-active, I guess I need two physically disparate load balancers that heart beat with each other? I'm not really a network engineer, and I dont understand what happens to the packets when 1 data center goes down, in terms of routing around it?
Thanks for your time.
- jwilliams 18y ago> In terms of active-active, I guess I need two physically disparate load balancers that heart beat with each other? Yeah - as the brk indicates in his post, you can use something like haproxy to do this. Afaik, you can get Apache to do this too... One advantage might be that Apache can be configured to do "sticky sessions" - which you'll need if you're not sync'ing sessions between sites (which in this scenario doesn't seem necessary). Never used haproxy, but it might do this too. In terms of your active-active setup, you can have two "legs" that are load balanced at the front, or you can have load balancing between each tier. If you're (a) not very experienced or (b) you don't have lots of bandwidth between sites, I'd go with the former and just have load balancing at the front end.
- bprater 18y agoAgreed, this is the type of information that is tough to find elsewhere, since it tends to be somewhat specialized. So for everyone posting -- thanks!