How Service Protection API Limits are enforced

How Service Protection API Limits are enforced

 Reference

Service protection API limits are enforced based on three facets:

• The number of requests sent by a user.
• The combined execution time required to process requests sent by a user.
• The number of concurrent requests sent by a user.

If the only limit was on the number of requests sent by a user, it would be possible to bypass it. The other facets were added to counter these attempts. For example:

• You could send fewer requests by bundling them in batch operations.
  • The combined execution time limit will counter this.
• Rather than sending requests individually in succession, you could send a large number of concurrent requests before service protection API limits are enforced.
  • The concurrent request limit will counter this.

Each web server available to your environment will enforce these limits independently. Most environments will have more than one web server. Trial environments are allocated only a single web server. The actual number of web servers that are available to your environment depends on multiple factors that are part of the managed service we provide. One of the factors is how many user licenses you have purchased.

The following table describes the default service protection API limits enforced per web server: