Multi server deployment

In large environments, accurately predicting the load from tasks and operations can be challenging. For any scenario involving high load and/or the need for high availability, consider your environment as Extra-Large (XLarge) and follow the recommendations provided below.

Cayosoft strongly recommends configuring multiple servers to distribute load effectively and ensure high availability. If required, join servers into Replication Groups to optimize performance and redundancy. Learn more about configuration tips here: Recommendations for XXL Environments.

Scenarios for high-load environments

High load on web portal

This scenario applies when the Web Portal is heavily used, creating significant load on the system. For example:

• High number of Helpdesk administrators: More than 100 helpdesk administrators daily accessing the Web Portal.

  NOTE: Helpdesk administrators generate more load than regular users. For example, 1 helpdesk administrator can produce the same load as up to 30 regular users with Self-Service Password Reset enabled.

• Self-Service usage: Approximately several hundred users actively using the Web Portal daily.

  NOTE: For environments with several hundred active users daily, especially those who access the portal within a short time frame (e.g., within 1 hour at work), Cayosoft recommends using multiple servers to ensure optimal performance and availability.

RECOMMENDED: Configure more than one Administration Service and Web Portal to distribute the load effectively.

High load on automation tasks

This scenario applies when Cayosoft Administrator is performing frequent, resource-intensive automation tasks.

Examples of high automation load

• Frequent group updates: Groups updated hourly.

• License updates: Microsoft 365 license assignments or updates performed within an hour.

• User Provisioning: High-frequency user provisioning tasks running hourly.

• Extremely large number of groups: Several thousands or more groups updated daily.

• High frequency of rules and runbooks execution: Resource-intensive automation modules executed multiple times per day.

RECOMMENDED: Configure a dedicated server for automation tasks. This ensures automation load does not affect Web Portal performance.

Mixed load scenarios (Web and Automation combined)

If your environment includes both heavy Web Portal usage and frequent automation tasks, a mixed configuration is required.

RECOMMENDED: Configuration for mixed load:

• Two servers for Web Portal:

  • These servers handle Web Portal traffic exclusively (subscriber servers).

  • Ensure that no automation tasks run on these servers.

• Dedicated server for automation (Publisher):

  • Configure all automation tasks, rules, and runbooks on a separate Publisher server.

  • Do not include the Publisher server in Web Portal traffic to avoid performance degradation.

Summary of multi-server configuration