Jump to content

Site Architecture Update - New Load Balancing and High Availability


RadioRob
This topic is 784 days old and is no longer open for new replies.  Replies are automatically disabled after two years of inactivity.  Please create a new topic instead of posting here.  

Recommended Posts

As of late yesterday, I have setup a new load balanced environment for the website.   So we now have two servers serving requests when you attempt to make a request.  This means that when I'm doing things like updating Apache, PHP or doing other server level tasks, our load balancer will route requests automatically to the other server.  This is the start of being able to setup a highly available site.  (The database and search functionality are still single threaded, but are less likely to be problematic and I can address this more in a later phase.)

Our two primary web servers are named Hooboy (#1) and Daddy (#2).

If you're curious about the high level architecture, the data flow for www.companyofmen.org looks like:

image.png

 

When requests come in, the load balancer sends half of requests to each server.  Literally as people have been using the site today, half of the time Hooboy answered and half the time Daddy answered.  If I ever lose one of those two servers, or need to work on one...  within 40 seconds, all requests will go to the other keeping us online.  

Prod-Web-1 (Hooboy)

image.png

Prod-Web-2 (Daddy)

image.png

Link to comment
Share on other sites

This topic is 784 days old and is no longer open for new replies.  Replies are automatically disabled after two years of inactivity.  Please create a new topic instead of posting here.  

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...