The key benefits of a master-slave setup with a high Web Access load are as follows:
An organization that has a high Web-based data access load can deploy this setup. In this case, the Web Access application is set up on a separate physical server. This server serves all the user Web requests and reduces the load of iFolder server that serves the back-end data. All the user requests are received by the Web Access server, which can be a publicly accessible server. The actual iFolder server is deployed within the organization firewall.
All communication to the Web Access server can be SSL-enabled.The communication between the Web Access server and the iFolder server can also be SSL-enabled if a secure channel is required between these servers.
The number of hits per second to the Web Access server through a browser is based on the server processing capability and the network link. A iFolder Web Access server does not limit the number of hits because it runs behind Apache and Apache governs the processing capability. The recommended number of hits per second is around 1000, which means 1000 simultaneous connections from users can exist at any time.
The hits to the Web Access server do not need to translate to requests to the iFolder server. The iFolder server capability is about 1000 simultaneous requests in a medium server class machine. If the H/W is higher, this capability can be increased.
Multiple Web Access servers can be configured in a multi-server iFolder setup, which means that each iFolder server (master or slave) can have its own Web Access server.