Versions Compared

Version Old Version 1 New Version Current
Changes made by

annaslc

mhodges

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Primary Architect: Michael Hodges

Description:   

 A load balancer is a device that distributes application or system traffic across a number of servers.  Load Balancing provides for redundancy and for horizontal scalability.  Redundancy helps ensure that an application is resilient to failures.  Horizontal scalability allows for capacity to be expanded by the addition of application instances.  Load Balancing can be accomplished with dedicated hardware appliances or with software.

 

Experimental

 

Strategic (3-5 Years)

  • F5 Networks BIG-IP Local Traffic Manager 4000 Load Balancing Devices

Tactical (1-2 Years)

  • F5 Networks BIG-IP Local Traffic Manager 4000 Load Balancing Devices

Containment

  • Web/Application Load Balancing

    • KFS uses Apache web server to handle balancing

    • PeopleSoft and SAS (and perhaps other applications) require application-specific load balancing

Retirement

 

 

Background:

  • Traditionally, ITS has used load balances in an “active/passive” configuration.  In this model, if the active environment becomes unavailable, processing is handed off to the passive (secondary) environment.

  • ITS has also used “round robin” load balancing for some applications.  This is a simple model where load is balanced in the order that requests come in. This technique has some value, but can still result in unbalanced situations.

  • In the future ITS will rely more and more on advanced balancing features. Advanced balancing is more intelligent about where connections are routed to better ensure that load is equally balanced across environments.  For example, if one server has high CPU utilization, load balancing may focus connections on the other environment.

...