The most common deployment configuration of NCache is as following:
2 or More Cache Servers
This installs both server and client portion of NCache software. You must install this on 2 or more servers for reliability. These can be dedicated servers or your web/app servers. For 3 or more web/app server environments, we recommend a dedicated caching tier. In this case, we recommend a 4:1 or 5:1 ratio between web/app servers and cache servers.
If you're installing NCache server on your web/app servers, then make sure you have sufficient memory and CPU power available for both your application and NCache.
This installs the remote client libraries along with client cache. Install this on all your web/app servers from where you want to remotely access the cache servers. Do not install it on cache servers.
This installs the NCache API, online help/documentation, and a local stand-alone cache without any clustering capability. Please note that you cannot access a remotely hosted cache from a developer machine. You can access only a local cache.
Note the following limitations for Developer Installation Type while connecting to remote caches:
Throttling of 50 requests/sec for each client: All such clients that are licensed under DEV license will not be able to make more than 50 requests/sec to the remote cache.
Limited number of requests (200,000) a client can send to remote cache: In a lifetime of client application in case it is licensed under DEV license, the client will stop making requests to remote cache after it has sent 200,000 requests to remote cache. The only work around is to restart application for another 200,000 requests. Once the client has made 200,000 requests, a licensing exception will be thrown saying “Clients running under DEV license cannot send more than 200,000 requests to remote cache.”
Developer licensed clients can make requests to local caches without any limitation.
Please refer to the Installation Guide for more detail on Installation.