The Visitor Prioritization Cloudlet helps maintain business continuity for your dynamic applications in high-demand situations by placing visitors in a virtual waiting room or your origin based on configured rules. It acts as a front-end “shock absorber” when peak traffic volumes require the origin for transaction processing, such as; shopping cart check-outs, donation pages, service/application subscriptions, and form registrations.

📘

Visitor Prioritization and Virtual Waiting Room cloudlets

Visitor Prioritization uses probability and percentage based prioritization for entry into the waiting room and origin. The Virtual Waiting Room cloudlet uses First In First Out (FIFO). FIFO is a fair request processing mechanism. Virtual Waiting Room and Visitor Prioritization Comparison provides the differences between these two cloudlets so that you can select the waiting room cloudlet that best meets your business requirements.

Workflow

The following diagrams show how Visitor 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: waiting room pages

What can you do if you want different waiting room pages for different waiting room experiences?

When you configure a Visitor Prioritization instance in Property Manager, you can specify the location of the waiting room asset, which, in effect, allows you to provide different waiting room experiences.

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