04-23-2019 07:10 AM
What is the hardware requirement to deploy NSS in terms of servers etc.
Solved! Go to Solution.
04-23-2019 07:24 AM
The general advice on server system resources is as follows. NSS system requirements tend to reflect the system requirements of the platforms it is installed on (Windows, IIS, SQL):
Small
Medium
Large
VM profile:
Networking considerations are:
Cloud databases:
Load balancers for NSS tend to be for emergency failover rather than actual load balancing nowadays as the system is relatively lightweight and the number of web requests for most of our customers relatively low. So this decision may be driven more by how important it is to keep the system online rather than based on the overall load. Additional balanced servers can also be configured in later if you wanted to start with just one.
Additional Information
When assessing the load, this would be related to the number of concurrent requests rather than the number of users. However, generally customers are primarily using one web server and one database server to deliver the application. The exceptions are where the customer has corporate policies that require them to implement the system to provide load balancing or high availability (active-passive web, clustered DB). As such, the categories can be considered as follows:
Its extremely rare for customers to require to balance load in NSS, even those that have tens of thousands of users. Medium would be our recommendation for customers unless corporate policies meant a need to implement additional policies as mentioned above for Large customers.
NSS can handle active-active and active-passive configurations for load servers. Active-passive is easily the most common implementation as customers tend to use LBs for high availability rather than actual load balancing.
There is no specific advice on actual load balancers but transparency is a requirement, so as long as URLs are passed through the load balancer appropriately, the system should work as expected.
04-23-2019 07:12 AM
04-23-2019 07:24 AM
The general advice on server system resources is as follows. NSS system requirements tend to reflect the system requirements of the platforms it is installed on (Windows, IIS, SQL):
Small
Medium
Large
VM profile:
Networking considerations are:
Cloud databases:
Load balancers for NSS tend to be for emergency failover rather than actual load balancing nowadays as the system is relatively lightweight and the number of web requests for most of our customers relatively low. So this decision may be driven more by how important it is to keep the system online rather than based on the overall load. Additional balanced servers can also be configured in later if you wanted to start with just one.
Additional Information
When assessing the load, this would be related to the number of concurrent requests rather than the number of users. However, generally customers are primarily using one web server and one database server to deliver the application. The exceptions are where the customer has corporate policies that require them to implement the system to provide load balancing or high availability (active-passive web, clustered DB). As such, the categories can be considered as follows:
Its extremely rare for customers to require to balance load in NSS, even those that have tens of thousands of users. Medium would be our recommendation for customers unless corporate policies meant a need to implement additional policies as mentioned above for Large customers.
NSS can handle active-active and active-passive configurations for load servers. Active-passive is easily the most common implementation as customers tend to use LBs for high availability rather than actual load balancing.
There is no specific advice on actual load balancers but transparency is a requirement, so as long as URLs are passed through the load balancer appropriately, the system should work as expected.