[Waiting Room] Add architecture info

Author: kodster28

src/content/docs/waiting-room/about.mdx

@@ -3,56 +3,45 @@ title: About
 pcx_content_type: concept
 sidebar:
   order: 2
-head:
-  - tag: title
-    content: About Waiting Room
 
 ---
 
 import { LinkButton, Render } from "~/components"
 
-Cloudflare Waiting Room protects websites by queueing site visitors when a website experiences unmanageable surges in legitimate traffic that may otherwise bring an application down.
+Waiting Room queues visitors when your traffic approaches a previously defined threshold that might otherwise bring an application down.
 
-<Render file="non-contract-enablement" product="fundamentals" />
+![Waiting Room process flow showing how a request is managed by Cloudflare and placed in a waiting room before reaching the origin website](~/assets/images/waiting-room/waiting-room-process-flow.png)
 
-## Benefits
+## User flow
 
-Waiting Room protects your origin server by preventing surges in legitimate traffic that may overload your origin.
+Once you have [created and activated a waiting room](/waiting-room/get-started/) for a specific application page:
 
-Waiting Room also benefits your visitors by:
+- If a page is not experiencing heavy traffic, a visitor accesses the page directly.
+- If page traffic approaches a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
 
-* Keeping your application online and preventing them from reaching error pages.
-* Showing estimated wait times that are continuously updated.
-* Opening up new spots more quickly by tracking dynamic inflow and [outflow](/waiting-room/reference/configuration-settings/#session-duration).
-* Remembering each visitor's status to prevent someone from losing their place in line or having to re-queue if they leave your site.
-* Appearing in your own [branding and style](/waiting-room/how-to/customize-waiting-room/), which enhances trust and lets you provide additional information as needed.
+  - Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
+  - While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
+  - When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
+  - Because waiting rooms support dynamic inflow and [outflow](/waiting-room/reference/configuration-settings/#session-duration), new spots appear more quickly and estimated wait times are lower and more accurate.
 
-## How it works
+## Architecture
 
-Once you have [created and activated a waiting room](/waiting-room/get-started/) for a specific application page:
+Waiting Room is built on [Workers](/workers/) that runs across a global network of Cloudflare data centers.
 
-* If a page is not experiencing heavy traffic, a visitor accesses the page directly.
-* If page traffic crosses a [user-defined threshold](/waiting-room/reference/configuration-settings/#session-duration), a visitor enters a virtual waiting room until it is their turn to access the page:
-  * Each user receives a [cookie](/waiting-room/reference/waiting-room-cookie/) to manage the dynamic outflow of requests from the waiting room to the origin website in [First In First Out (FIFO)](/waiting-room/reference/queueing-methods/#first-in-first-out-fifo) order.
-  * While in the waiting room, the user's browser automatically refreshes every 20 seconds to give them updated information about their estimated wait time.
-  * When a user exits the waiting room and reaches your application, they can leave and re-enter without waiting for the length of time specified by the [session duration](/waiting-room/reference/configuration-settings/#session-duration).
-  * Because waiting rooms support dynamic inflow and [outflow](/waiting-room/reference/configuration-settings/#session-duration), new spots appear more quickly and estimated wait times are lower and more accurate.
+When a request comes to a host or path covered by a Waiting Room, that request goes to a Waiting Room Worker in the closest geographic data center. The Worker then needs to make a decision: whether to send users to the queue or the website.
 
-![Waiting Room process flow showing how a request is managed by Cloudflare and placed in a waiting room before reaching the origin website](~/assets/images/waiting-room/waiting-room-process-flow.png)
+That decision itself depends on two factors: [admin-defined thresholds](/waiting-room/reference/configuration-settings/) and the Waiting Room state.
 
-## Availability
+For admin-defined thresholds, the two measures that matter are `total active users` and `new users per minute`:
 
-The following customers have access to Cloudflare Waiting Room:
+- `total active users` is a target threshold for how many simultaneous users you want to allow on the pages covered by your waiting room.
 
-* Those qualified under [Project Fair Shot](https://www.cloudflare.com/fair-shot/)
-* Customers on a Business or Enterprise plan
+- `new users per minute` defines the target threshold for the maximum rate of user influx to your website per minute.
 
-Access to certain features depends on a customer's [plan type](/waiting-room/plans/).
+A sharp spike in either of these values might result in queuing. Another configuration that affects how we calculate `the total active users` is `session duration`. A user is considered active for `session duration` minutes since the request is made to any page covered by a waiting room.
 
-## Prerequisites
+The other factor is the Waiting Room state, which is maintained at the local data center level but then also changes continuously based on the traffic around the world. Each data center works with its own Waiting Room state. This state is a snapshot of the traffic pattern for the website around the world available at that point in time. The advantage of using this approach - making decisions at the Worker level - is that we can make decisions without any significant latency added to the request. The algorithm for Waiting Room dynamically allocates a certain number of slots available to each Worker based on the Waiting Room state. Queueing starts when the slots run out within the Worker. The lack of additional latency added enables the customers to turn on the waiting room all the time without worrying about extra latency to their users.
 
-* [Cloudflare’s CDN](/cache/) is required to use the Waiting Room feature.
-* Configure a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) or a [proxied load balancer](/load-balancing/understand-basics/proxy-modes/) for the waiting room’s hostname. A DNS record is not auto-configured after a waiting room is created.
-* Visitors must enable cookies. Refer to [Waiting Room cookies](/waiting-room/reference/waiting-room-cookie/) for information on how cookies are used in Cloudflare Waiting Room.
+The Waiting Room state is updated with global information every few seconds. We have a pipeline set up in Cloudflare [Durable Objects](/durable-objects/) that ensures changes in traffic get propagated around the world. This architecture ensures that we do not introduce additional latency, as well as that we are making decisions with as near-time accuracy as possible.
 
- <LinkButton variant="primary" href="/waiting-room/get-started/">Get started</LinkButton>
+For even more details about the architecture and why we made these decisions, refer to our [deep-dive technical blog](https://blog.cloudflare.com/how-waiting-room-queues).

src/content/docs/waiting-room/index.mdx

@@ -9,11 +9,11 @@ head:
 
 ---
 
-import { CardGrid, Description, Feature, LinkTitleCard, Plan, RelatedProduct } from "~/components"
+import { CardGrid, Description, Feature, LinkTitleCard, Plan, RelatedProduct, Render } from "~/components"
 
 <Description>
 
-A virtual waiting room to manage peak traffic. 
+A virtual waiting room to manage peak traffic.
 </Description>
 
 <Plan type="business" />
@@ -22,42 +22,77 @@ Cloudflare Waiting Room allows you to route excess users of your website to a cu
 
 ***
 
+## Benefits
+
+Waiting Room protects your origin server by preventing surges in legitimate traffic that may overload your origin.
+
+Waiting Room also benefits your visitors by:
+
+- Keeping your application online and preventing them from reaching error pages.
+- Showing estimated wait times that are continuously updated.
+- Opening up new spots more quickly by tracking dynamic inflow and [outflow](/waiting-room/reference/configuration-settings/#session-duration).
+- Remembering each visitor's status to prevent someone from losing their place in line or having to re-queue if they leave your site.
+- Appearing in your own [branding and style](/waiting-room/how-to/customize-waiting-room/), which enhances trust and lets you provide additional information as needed.
+
+---
+
 ## Features
 
 <Feature header="Scheduled Event" href="/waiting-room/additional-options/create-events/">
-Customize the behavior of a waiting room for a specific period of time. 
+Customize the behavior of a waiting room for a specific period of time.
 </Feature>
 
 <Feature header="Waiting Room Rules" href="/waiting-room/additional-options/waiting-room-rules/">
-Create rules to indicate specific traffic or areas of your site or application that you do not want a waiting room to apply to. 
+Create rules to indicate specific traffic or areas of your site or application that you do not want a waiting room to apply to.
 </Feature>
 
 <Feature header="Waiting Room Analytics" href="/waiting-room/waiting-room-analytics/">
-Get insights into the traffic going through your waiting room. 
+Get insights into the traffic going through your waiting room.
 </Feature>
 
 <Feature header="Additional hostname and path coverage" href="/waiting-room/how-to/place-waiting-room/">
-Apply a single waiting room to multiple hostnames and paths within the same zone. 
+Apply a single waiting room to multiple hostnames and paths within the same zone.
 </Feature>
 
 ***
 
 ## Related products
 
 <RelatedProduct header="Cloudflare for SaaS" href="/cloudflare-for-platforms/cloudflare-for-saas/" product="cloudflare-for-platforms">
-Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare’s network to your customers via their own custom or vanity domains. 
+Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare’s network to your customers via their own custom or vanity domains.
 </RelatedProduct>
 
 <RelatedProduct header="Rules" href="/rules/" product="rules">
-Cloudflare Rules allows you to make adjustments to requests and responses, configure Cloudflare settings, and trigger specific actions for matching requests. 
+Cloudflare Rules allows you to make adjustments to requests and responses, configure Cloudflare settings, and trigger specific actions for matching requests.
 </RelatedProduct>
 
 <RelatedProduct header="SSL/TLS" href="/ssl/" product="ssl">
-Cloudflare SSL/TLS encrypts your web traffic to prevent data theft and other tampering. 
+Cloudflare SSL/TLS encrypts your web traffic to prevent data theft and other tampering.
 </RelatedProduct>
 
 ***
 
+## Availability
+
+The following customers have access to Cloudflare Waiting Room:
+
+- Those qualified under [Project Fair Shot](https://www.cloudflare.com/fair-shot/)
+- Customers on a Business or Enterprise plan
+
+Access to certain features depends on a customer's [plan type](/waiting-room/plans/).
+
+<Render file= "non-contract-enablement" product="fundamentals" />
+
+***
+
+## Prerequisites
+
+- [Cloudflare’s CDN](/cache/) is required to use the Waiting Room feature.
+- Configure a [proxied DNS record](/dns/manage-dns-records/how-to/create-dns-records/) or a [proxied load balancer](/load-balancing/understand-basics/proxy-modes/) for the waiting room’s hostname. A DNS record is not auto-configured after a waiting room is created.
+- Visitors must enable cookies. Refer to [Waiting Room cookies](/waiting-room/reference/waiting-room-cookie/) for information on how cookies are used in Cloudflare Waiting Room.
+
+***
+
 ## More resources
 
 <CardGrid>