Load Balancing for Desktop Synchronization

Available from Version: 9.3

Operating System: Windows, macOS

Required Permissions: User

During the desktop synchronization via the empower^® Sync, empower^® uses a load balancing system to balance out the synchronization load.

For further information regarding the empower^® Sync and its user interface, see empower^® Sync.

If too many clients try to synchronize at the same time, this can lead to peak loads on the application server. There can be various reasons for this. Examples of this situation are the following:
Many employees log in when starting to work in the morning at the same time. Many new employees log in when starting to work at the beginning of the month. Many devices synchronize at the same time because of an update that has been distributed.
During such load peaks, the application server may no longer respond to device requests quickly enough. Despite multiple requests from a device, this can lead to the synchronization process being aborted on the devices. After a few minutes, the devices try to synchronize again. This creates a traffic jam as more and more devices try to synchronize at the same time.
To avoid such overload situations on the application server, each device coordinates with the backend before starting a synchronization process. The backend only approves an adequate number of parallel synchronization processes. As soon as the maximum possible number of parallel synchronization processes is reached, the backend denies synchronization to further requesting devices and places them in a queue. The user receives a corresponding notification in the empower^® Sync user interface and the client attempts to restart synchronization after the specified time.

A collaborative approach is taken with regard to installations of lower versions.

This means that devices with older versions can still synchronize, but they are not compatible with the load balancing concept.

Therefore, all synchronization requests from older versions are accepted by the backend.