Example Deployment Scenarios#
The following scenarios provide a generalized deployment scenario based on your identified usage pattern. This is a high level representation to guide you on how you might approach deployment of ARGUS Enterprise.
Warning
These are example scenarios to give you a starting point for determining what is most important to size. This should be taken as a guide, and adjusted as your needs dictate.
Very Light Load
Very Light Load#
Very Light load with shared common resources is only appropriate for environmnts with little bulk activity and smaller database size. Due to the shared server environemnt, this type of environment is subject to contention and performance issues once activity increases beyond light usage.
Tip
Consider adjusting the number of simultaneous threads running bulk operations in this shared server environment. This can help reduce the impact on SQL & App Service. The recommendation of 1.5 * NumberOfCores is typically for a standalone Process Server. When installed on a shared environment reducing the ratio to 0.5-1x the number of cores could help reduce the impact of the Process Server operations.
| Area | Sizing Resources |
|---|---|
| App Server | Basic Specs |
| Proc Server | Basic Specs |
| SQL Server | Basic SQL Specs - Basic SSRS Specs |
Tip
It’s possible to install the App, Proc, and SQL Server on the same server. There are potential issues if you increase the load on the server, but it may work fine for your environment if very light usage. For detailed testing notes on this, see the FAQ.
Light Load
Light Load#
Light usage will require less detailed analysis on sizing to ensure properly size. Since system resources will not be as heavily impacted basic sizing should suffice. It is recommended to consider in more detail the following sections:
| Area | Sizing Resources |
|---|---|
| App Server | Basic Specs |
| Proc Server | Basic Specs |
| SQL Server | Basic SQL Specs - Basic SSRS Specs |
Tip
It’s possible to install the App, Proc, and SQL Server on the same server. There are potential issues if you increase the load on the server, but it may work fine for your environemnt if very light usage. For detailed testing notes on this, see the FAQ.
Moderate Load
Moderate Load#
Moderate usage load will require a slightly more detailed analysis of sizing to ensure properly size. It is recommended to consider in more detail the following sections:
| Area | Sizing Resources |
|---|---|
| App Server | App Server Sizing |
| Proc Server | Proc Server Sizing |
| SQL Server | - SQL Server Sizing - SSRS Server Sizing Or Basic Specs |
Heavy Load
Heavy Load#
Heavy usage load will require more detailed analysis of sizing to ensure properly size. It is recommended to consider in more detail the following sections:
| Area | Sizing Resources |
|---|---|
| App Server | App Server Sizing |
| Proc Server | Proc Server Sizing |
| SQL Server | - SQL Server Sizing - SSRS Server Sizing |
Other Deployment Scenarios#
Tip
There are various approaches to deployment, which will vary based on business requirements and desired scalability. The following examples should be taken as additional examples of infrastructure variations to help understand the architecture for a deployment.
