F5 Distributed Cloud (XC) Origin server subset rules provide the ability to create match conditions on incoming source traffic to the HTTP load balancer. The match conditions include Country, ASN, Regional edge (RE), IP address, and client label selectors for subset selection of destination (origin servers). This helps in customized routing based on request information.
As there is a decent increase in Holiday retail sales every year, which leads to an increase in ecommerce shopping during Thanksgiving, Cyber Monday, and Holiday season as well. It is observed that there is a spike in web traffic to 38% and Black Friday sees 3x the traffic than normal days during this time frame, and this has led to 1.7 billion online visits during the global holiday season. Under these circumstances, users in certain locations consume more than 50% of global traffic. An event of this nature requires infrastructure that must easily scale up to match the surge in traffic.
One of the most suitable solutions for this challenge is to identify the users’ demands and their geographical location and distribute the traffic by increasing further bandwidth to the existing or new servers. This diversification in traffic based on geo location helps the users to access the application specifically for their immediate needs there by avoiding wait time or outages during this period.
This is achieved using F5 XC Origin Server Subset rules, which helps to redirect the traffic based on Geo Location with subset rules.
Below are the steps to be followed to redirect the traffic that helps in solving the situation mentioned above,
Step 1: Creating a label (key-value pair).
Step 2: Adding labels to one or more Origin Servers.
Step 3: Creating subset rule in Load Balancer.
This rule helps in redirecting the traffic from the countries mentioned below to use different servers apart from the server allotted for United States, thereby providing more Bandwidth to the Users in United States.
It is observed from the above logs that the users from US Geo location directed as per Origin Server Label associated with it.
Whereas the users apart from US get load-balanced to different Origin Server as mentioned in Origin Pool as per Label configs.
Thereby, users in the US could be able to experience the enhanced capability of their allocated servers. This helps in avoiding outages, bottlenecks.
Note: Given requirement can also be achieved using RE match condition as well by adding necessary REs as shown below.
F5 XC analyzes the traffic based on its origin, such as Regional Edges, Geo Location, IP Match and more and redirects the traffic as per Origin Server Subset Rules configuration. This simple and effective technique could be able to meet the users’ demands in no time and helps in solving major issues during peak usage hours of e-commerce sites.
Hello to Everyone,
After my investigation of the OpenAPI/Swagger options for AWAF/ASM that I have questions under F5 AWAF/ASM support for wildcard url and parameter... - DevCentral that I have still have questions now I have the same questions for XC Swagger/OpenAPI supported custom options and if there is a list?
I see that XC supports Regex for wildcard in the path as shown below but what about parameters with wildcard names or if there could be a wildcard support for methods as to not have to specify each method under an http path or using custom word like "any" ? Other than that it will be nice if there is support for parameters to be specified as in any location not query or request body.
Any help will appreciated.
"description": "Numeric ID of the user to get"
This article wouldn’t have been the same without the efforts of @Fouad_Chmainy, @Matt_Dierick, and Alexis Da Costa. They are the original authors of the distributed design, the Sentence app, and the NGINX Plus OIDC image optimized for Distributed Cloud. Additionally, special thanks to @Cody_Green and @Kevin_Reynolds for inspiration and assistance in the Terraform portion of the solution. Thanks, guys!
Table Of Contents:
An open group to foster discourse around the integration of security, networking, and application management services across public/private cloud and network edge compute services.