Description
In high traffic networks, servers can experience overwhelming workloads, impacting performance which in turn, impacts users. Load balancing is a method of distributing the load across multiple identical servers, improving server-side performance and reducing the impact on users.
Content Manager typically operates as a direct client to server connection, with users connecting to a single server, with a backup option configurable as a fallback. Whilst this can provide a level of redundancy, as all users are connecting to the primary workgroup server first, there is the potential for the server to be overloaded.
To enable load balancing for Content Manager, external solutions are required.
Load balancing server
This is a virtual server sitting between the client machines and Content Manager workgroup servers. The load balancing server will split and redirect traffic to the required servers based on its configuration.
Pros
- Easier administration
- Easier setup
- More configurable
Cons
- Slower network performance as there is another layer between the client and Content Manager workgroup server
DNS Round-Robin
A network rule that nominates two or more IP addresses to a single domain name. When users connect to that address, the destination server is chosen in a round-robin fashion using the associated IP addresses.
Pros
- Does not impact network performance as it does not add a new layer, just alternates connections
Cons
- Not as configurable
- Not as easy to administer
Consideration when configuring load balancing for Content Manager?
Each Content Manager workgroup server included in the load balancing must be configured identically. Any changes made on one of these servers must be reflected on the other.
This goes down to the application level, if the configuration of an application on one of these servers is altered, the same change must be made on all servers.
For example, if the Content Manager web client on 'server a' had its configuration adjusted to allow for larger file sizes, then the configuration of the Content Manager web client on 'server b' would require the same change.