We often receive questions on how much traffic AccessAlly can handle, in terms of visitors, login volume, etc.For example: Is it feasible that would should ever be able to handle the load of 10K+ people logging in at one time and several thousand registering (and creating a user) at the same time? If possible, what would it take? (ie a server configuration with load balancing in place etc?).
ARTICLE CONTENT:
Server Requirements
As long as the server is decently provisioned, traffic volume (including visitor / login volume) should NOT be an issue with AccessAlly.
(What constitutes the “decently provisioned” part does vary from server to server. Please see this article for more information on choosing the right LMS hosting provider for your needs.)
Ranking of Operations by Their Stress on the Server
From least to greatest, here is a list of how each operation instigated by AccessAlly will affect your server:
1. Local page access (visiting content pages, logging in): these requests are 100% handled by the web server/hosting provider. If you are seeing an excessive server errors, then the server likely needs to be upgraded.
2. AccessAlly-triggered API operation (On-Demand login, order form login creation): these requests involve API interactions with your CRM.
3. CRM-triggered operation (webhooks): the operation itself is the same as #2, but it requires an extra step of the CRM sending out the webhook.
In addition, there are a couple of “unknown” factors:
a. CRM opt-in form: if you are looking at more than 1 opt-in per second, it might be a good idea to let your CRM know, so they can tell you whether they can handle such volume.
b. CRM API rate limit: usually CRMs have a limit, but the documentation may not be available to give a specific number.
