Capacity Planning & Sizing

proper capacity planning ensures that your activate environment performs reliably and scales effectively as your organisation grows this guide outlines the key considerations and recommendations for sizing your activate infrastructure overview activate is a multi tier platform consisting of the following core components web portal – the main user interface and api endpoint orchestrator service – handles background processing, workflows, and automation sql database – stores configuration data, workflow definitions, history, and cached directory information activate studio – desktop management tool used by administrators for configuration and maintenance activate anywhere – lightweight proxy component that provides secure external access for mobile and remote users when required each component can be installed on a single server for smaller environments or distributed across multiple servers for scalability and performance key sizing factors the appropriate sizing for activate depends on several factors factor description number of users total number of concurrent and total users accessing the platform automation load volume and frequency of background tasks, workflows, and provisioning jobs directory size number of active directory objects synchronised (users, groups, contacts, etc ) integration complexity number and frequency of connector operations with external systems audit and logging requirements retention period and verbosity of system logs and history tables recommended starting point the following provides a general baseline for a typical mid sized environment component recommended specification notes windows server windows server 2019 or later virtual or physical vcpus 4–8 allocate more cores for large automation loads memory 16–32 gb ram increase if connectors or cache size are high disk 200 gb ssd separate data and log volumes recommended sql server sql server 2019 or later dedicated or shared instance network low latency connection between web, orchestrator, and database servers use same data centre or virtual network scaling recommendations as usage increases, activate can be scaled both vertically (by increasing server resources) and horizontally (by adding servers) vertical scaling add more cpu and memory to the existing vm increase sql server iops and memory allocation extend disk space to accommodate log growth and caching horizontal scaling separate web and orchestrator roles onto dedicated vms use a load balancer for multiple web servers to improve resilience deploy a dedicated sql server or sql cluster for larger environments install activate anywhere on a separate host if supporting large numbers of external users performance and monitoring to ensure consistent performance monitor system metrics such as cpu, memory, and disk i/o review orchestrator job throughput and queue times track sql performance using built in monitoring tools or your organisation’s preferred solution archive or purge logs regularly to maintain optimal database performance storage considerations use fast ssd storage for both web and database servers allocate a separate volume for sql transaction logs plan for regular backups of the activate database and configuration directories assistance and review your activate representative can assist with capacity assessments and provide guidance tailored to your deployment model and usage expectations it is recommended to review capacity annually or following any major expansion of activate’s use within your organisation these figures are intended as a starting point actual requirements depend on your organisation’s size and workload