System and methods to effectively route traffic and proactively scale infra in the partner region

1. A traffic routing and infrastructure scaling system comprising:

a processor and a computer readable medium operably coupled thereto, the computer readable medium comprising a plurality of instructions stored in association therewith that are accessible to, and executable by, the processor, to perform operations which comprise:

receiving, by a primary region, incoming customer requests;

determining, by a traffic control module, a traffic redirect quotient (TRQ) and a regional scale quotient (RSQ), wherein the TRQ indicates a percentage of the incoming customer requests needed to be redirected to a secondary partner region and the RSQ indicates a percentage of infrastructure scaling needed in the secondary partner region;

receiving, by a recommendation processing module, the TRQ and the RSQ;

automatically initiating, by the recommendation processing module, redirection of the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region, scaling the percentage of infrastructure indicated by the RSQ in the secondary partner region, or both; and

routing, by a network traffic manager service, the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region.

2. The traffic routing and infrastructure scaling system of claim 1 , wherein the operations further comprise:

determining, by an infrastructure breach indicator (IBI) module, a plurality of infrastructure-related metrics;

calculating, by an incoming traffic breach indicator (ITBI) module, a percentage of traffic load breach; and

determining, by an application breach indicator (ABI) module, a number of critical errors, a percentage of leading errors, and health of an application.

3. The traffic routing and infrastructure scaling system of claim 2 , wherein the operations further comprise uploading the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application to a cache.

4. The traffic routing and infrastructure scaling system of claim 3 , wherein determining the TRQ and RSQ comprises retrieving, from the cache, the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application.

5. The traffic routing and infrastructure scaling system of claim 4 , wherein the TRQ is determined to be equal to the percentage of the traffic load breach.

6. The traffic routing and infrastructure scaling system of claim 5 , wherein the RSQ is determined to be 100% when the number of critical errors is greater than zero, or when there is a health check failure.

7. The traffic routing and infrastructure scaling system of claim 6 , wherein the plurality of infrastructure-related metrics comprise a percentage of automatic scaling used, a percentage of central processing unit (CPU) used, a percentage of memory used, and a percentage of network used.

8. The traffic routing and infrastructure scaling system of claim 7 , wherein the TRQ is determined to be 100% when:

the number of critical errors is greater than zero; or

there is a health check failure; or

the percentage of automatic scaling is greater than 99% and the percentage of CPU used, the percentage of memory used, or the percentage of network used is greater than a threshold value.

9. The traffic routing and infrastructure scaling system of claim 7 , wherein the operations further comprise establishing a minimum percentage of infrastructure scaling for the secondary partner region.

10. The traffic routing and infrastructure scaling system of claim 9 , wherein the RSQ is determined to be a maximum of:

the minimum percentage of infrastructure scaling for the secondary partner region;

the percentage of automatic scaling used;

the percentage of leading errors;

the percentage of traffic load breach; or

when the percentage of autoscaling has crossed a threshold:

the percentage of CPU used,

the percentage of memory used, or

the percentage of network used.

11. A method for traffic routing and infrastructure scaling, which comprises:

receiving, by a primary region, incoming customer requests;

determining, by a traffic control module, a traffic redirect quotient (TRQ) and a regional scale quotient (RSQ), wherein the TRQ indicates a percentage of the incoming customer requests needed to be redirected to a secondary partner region and the RSQ indicates a percentage of infrastructure scaling needed in the secondary partner region;

receiving, by a recommendation processing module, the TRQ and the RSQ;

automatically initiating, by the recommendation processing module, redirection of the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region, scaling the percentage of infrastructure indicated by the RSQ in the secondary partner region, or both; and

routing, by a network traffic manager service, the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region.

12. The method of claim 11 , which further comprises:

determining, by an infrastructure breach indicator (IBI) module, a plurality of infrastructure-related metrics;

calculating, by an incoming traffic breach indicator (ITBI) module, a percentage of traffic load breach; and

determining, by an application breach indicator (ABI) module, a number of critical errors, a percentage of leading errors, and health of an application.

13. The method of claim 12 , which further comprises:

uploading the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application to a cache, and

wherein determining the TRQ and RSQ comprises retrieving, by the traffic control module from the cache, the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application.

14. The method of claim 13 , wherein the plurality of infrastructure-related metrics comprise a percentage of automatic scaling used, a percentage of central processing unit (CPU) used, a percentage of memory used, and a percentage of network used.

15. The method of claim 14 , wherein the TRQ is determined to be 100% when:

the number of critical errors is greater than zero; or

there is a health check failure; or

the percentage of automatic scaling is greater than 99% and the percentage of CPU used, the percentage of memory used, or the percentage of network used is greater than a threshold value.

16. The method of claim 14 , which further comprises establishing a minimum percentage of infrastructure scaling for the secondary partner region, and wherein the RSQ is determined to be a maximum of:

the minimum percentage of infrastructure scaling for the secondary partner region;

the percentage of automatic scaling used;

the percentage of leading errors;

the percentage of traffic load breach; or

when the percentage of autoscaling has crossed a threshold:

the percentage of CPU used,

the percentage of memory used, or

the percentage of network used.

17. A non-transitory computer-readable medium having stored thereon computer-readable instructions executable by a processor to perform operations which comprise:

receiving, by a primary region, incoming customer requests;

determining, by a traffic control module, a traffic redirect quotient (TRQ) and a regional scale quotient (RSQ), wherein the TRQ indicates a percentage of the incoming customer requests needed to be redirected to a secondary partner region and the RSQ indicates a percentage of infrastructure scaling needed in the secondary partner region;

receiving, by a recommendation processing module, the TRQ and the RSQ;

automatically initiating, by the recommendation processing module, redirection of the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region, scaling the percentage of infrastructure indicated by the RSQ in the secondary partner region, or both; and

routing, by a network traffic manager service, the percentage of the incoming customer requests indicated by the TRQ to the secondary partner region.

18. The non-transitory computer-readable medium of claim 17 , wherein the operations further comprise:

determining, by an infrastructure breach indicator (IBI) module, a plurality of infrastructure-related metrics;

calculating, by an incoming traffic breach indicator (ITBI) module, a percentage of traffic load breach; and

determining, by an application breach indicator (ABI) module, a number of critical errors, a percentage of leading errors, and health of an application.

19. The non-transitory computer-readable medium of claim 18 , wherein:

the operations further comprise uploading the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application to a cache, and

determining the TRQ and RSQ comprises retrieving, from the cache, the plurality of infrastructure-related metrics, the percentage of traffic load breach, the number of critical errors, the percentage of leading errors, and the health of the application.

20. The non-transitory computer-readable medium of claim 19 , wherein the plurality of infrastructure-related metrics comprise a percentage of automatic scaling used, a percentage of central processing unit (CPU) used, a percentage of memory used, and a percentage of network used.