For applications that call resources of various formats (like JSON or XML), API Prioritization lets you specify which calls are given priority and are sent to the origin during high-demand situations. Based on information in the inbound request, you configure the rules that determine which calls are prioritized.

Workflow

The following diagrams show how API Prioritization works both during normal traffic flow and during times when your application is experiencing a large amount of traffic.

Normal Traffic

Application Overload

Use case: Different Responses for Different End User Categories

When you add the API Prioritization behavior to a rule in Property Manager, you specify the location of the alternate response in NetStorage. However, what if you wanted to use a different response for each of your main categories of end users?

To accomplish this, you would complete the following tasks for each of the remaining end user categories:

How to

1. Set up a new rule, or child rule, within the same property.

2. Set up match criteria for the rule, making sure that it will match on the desired end user category.

📘

For information on how Property Manager handles rules, review the Property Manager on-line help.

3. Add the API Prioritization behavior to the new rule or child rule.

4. In the NetStorage field, select the path for the file that will serve as the alternate response.

5. Repeat steps 1 and 4 for each of the remaining user categories.

6. Save your changes to the property.

To learn more about Cloudlets basics, see:
How Cloudlets work
Cloudlets terminology
Property and Cloudlet policy considerations