Granted Patent B2

US 12,278,767 · App. 17/454,884 · Granted Apr 15, 2025

Inventors: Ravindra G. Gore (Fremont, CA); Benjamin Fry (Berkeley, CA); Chaitanya Bhatt (Fremont, CA)

Assignee: Salesforce, Inc.

H04L47/122H04L41/0816H04L41/0896H04L43/062H04L43/0876H04L43/0882H04L43/0888H04L43/16H04L47/25H04L47/30H04L41/22

Abstract

Claims (51)

1. A system comprising:

a server system comprising one or more processors in communication with one or more memory devices storing computer readable instructions that when executed by the one or more processors are configured to cause:

enabling a preconfigured waiting room site specific to a first site;

receiving, via an edge worker associated with a content delivery network (CDN), a first set of requests to access a first site;

determining that traffic to the first site is to be throttled;

responsive to determining that traffic to the first site is to be throttled, determining a throttling rate based at least in part on: a number of requests in the first set of requests and/or a degradation rate associated with a degradation in service capacity;

transmitting instructions to the edge worker, the instructions configured to cause the edge worker to direct at least a portion of a second set of requests to access the first site to the waiting room site prior to being directed to the first site, the direction of the at least the portion of the second set of requests to the waiting room site being subject to the throttling rate; and wherein the instructions to the edge worker comprise an indication of the throttling rate;

determining an update in performance due to throttling subject to the first throttling rate; and

determining whether to disable the preconfigured waiting room site based at least part on the update in performance.

2. The system of claim 1 , wherein the throttling rate is determined based on a number of requests for the first site at which the degradation in service capacity occurred.

3. The system of claim 2 , wherein the degradation in service capacity is identified based on a spike in CPU usage of the server system, a spike in CPU usage of an application server associated with the server system, and/or network usage information.

4. The system of claim 1 , and wherein the waiting room site was preconfigured prior to determining that the traffic to the first site is to be throttled.

5. The system of claim 1 , wherein the server system is further configurable to cause:

determining a response to throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause the waiting room site to be disabled and to cause a third set of requests to access the first site to be directed to the first site.

6. The system of claim 1 , wherein the server system is further configurable to cause:

determining a response to throttling of traffic to the first site;

determining an updated throttling rate based on the response to the throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause a third set of requests to access the first site to be throttled subject to the updated throttling rate.

7. The system of claim 1 , wherein the throttling rate is determined further based on traffic to a second site associated with the server system.

8. A non-transitory computer readable medium storing instructions that when executed by one or more processors is configurable to perform:

receiving, via an edge worker associated with a content delivery network (CDN), a first set of requests to access a first site;

determining that traffic to the first site is to be throttled;

responsive to determining that traffic to the first site is to be throttled, determining a throttling rate based at least in part on: a number of requests in the first set of requests and/or a degradation rate associated with a degradation in service capacity, wherein the degradation in service capacity is determined based on a spike in CPU usage of a server system associated with the first site or a spike in CPU usage of an application server associated with the server system; and

transmitting instructions to the edge worker, the instructions to the edge worker configured to cause the edge worker to direct at least a portion of a second set of requests to access the first site to a waiting room site prior to being directed to the first site, the direction of the at least the portion of the second set of requests to the waiting room site being subject to the throttling rate.

9. The non-transitory computer readable medium of claim 8 , wherein the throttling rate is determined based on a number of requests for the first site at which the degradation in service capacity occurred.

10. The non-transitory computer readable medium of claim 9 , wherein the degradation in service capacity is identified based on network usage information.

11. The non-transitory computer readable medium of claim 8 , wherein the waiting room site is specific to the first site, and wherein the waiting room site was preconfigured prior to determining that the traffic to the first site is to be throttled.

12. The non-transitory computer readable medium of claim 8 , wherein the instructions are configured to further cause:

determining a response to throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause the waiting room site to be disabled and to cause a third set of requests to access the first site to be directed to the first site.

13. The non-transitory computer readable medium of claim 8 , wherein the instructions are configured to further cause:

determining a response to throttling of traffic to the first site;

determining an updated throttling rate based on the response to the throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause a third set of requests to access the first site to be throttled subject to the updated throttling rate.

14. The non-transitory computer readable medium of claim 8 , wherein the throttling rate is determined further based on traffic to a second site associated with a datacenter that hosts the first site.

15. A method comprising:

receiving, via an edge worker associated with a content delivery network (CDN), a first set of requests to access a first site;

determining that traffic to the first site is to be throttled;

responsive to determining that traffic to the first site is to be throttled, determining a throttling rate based at least in part on: a number of requests in the first set of requests and/or a degradation rate associated with a degradation in service capacity, wherein the degradation in service capacity is determined based on a spike in CPU usage of a server system associated with the first site or a spike in CPU usage of an application server associated with the server system; and

transmitting instructions to the edge worker, the instructions configured to cause the edge worker to direct at least a portion of a second set of requests to access the first site to a waiting room site prior to being directed to the first site, the direction of the at least the portion of the second set of requests to the waiting room site being subject to the throttling rate.

16. The method of claim 15 , wherein the throttling rate is determined based on a number of requests for the first site at which the degradation in service capacity occurred.

17. The method of claim 16 , wherein the degradation in service capacity is identified based on network usage information.

18. The method of claim 15 , further comprising:

determining a response to throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause the waiting room site to be disabled and to cause a third set of requests to access the first site to be directed to the first site.

19. The method of claim 15 , further comprising:

determining a response to throttling of traffic to the first site;

determining an updated throttling rate based on the response to the throttling of traffic to the first site; and

transmitting updated instructions to the edge worker, wherein the updated instructions cause a third set of requests to access the first site to be throttled subject to the updated throttling rate.

20. The method of claim 15 , wherein the throttling rate is determined further based on traffic to a second site.

Assignments (2)

Continuity (1)

References Cited (229)