System and method for managing network traffic routing

• US 10,223,469 B2
• Filed: 03/23/2018
• Issued: 03/05/2019
• Est. Priority Date: 03/16/2006
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Pritchett, Daniel L, Flint, Ian, Yang, Connie Wong
• Primary Examiner(s): Swearingen, Jeffrey R
• Application Number:
  US15/934,418
• Publication Number:
  US 20180225385A1
• Time in Patent Office: 347 Days
• Field of Search: None
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04W 4/02 Services making use of location information

Abstract

Systems and methods for managing network traffic routing are described. The system receives network traffic from external-facing load balancers at a gateway of a distributed network application. The network traffic includes one or more data requests. The system inspects a data request of the one or more data requests to determine a context of the data request. The system routes the network traffic from the external-facing load balancers to the gateway based on a geographic location of an origin of the network traffic. Finally, the system routes, based on the context of the data request corresponding to data stored at a database, the data request from the gateway to a first internal-facing load balancer of a plurality of internal-facing load balancers associated with a first application server of a plurality of application servers having a closest geographic proximity to the database.

Claims

1. A system, comprising:

at least one processor and executable instructions accessible on a computer-readable medium that, when executed, cause the at least one processor to perform operations comprising;

receiving network traffic from a plurality of external-facing load balancers at a gateway of a distributed network application, the distributed network application including the plurality of external-facing load balancers, a plurality of gateways including the gateway, a plurality of internal-facing load balancers, a plurality of application servers, and a database, the plurality of gateways located between the plurality of external-facing load balancers and the plurality of internal-facing load balancers, the network traffic including one or more data requests;

inspecting a data request of the one or more data requests to determine a context of the data request;

routing the network traffic from the plurality of external-facing load balancers to the gateway based on a geographic location of an origin of the network traffic; and

routing, based on the context of the data request corresponding to data stored at the database, the data request from the gateway to a first internal-facing load balancer of the plurality of internal-facing load balancers associated with a first application server of the plurality of application servers based on at least geographic proximity of the first application server to the database.

2. The system of claim 1, wherein the gateway includes a configuration file, wherein the gateway utilizes the configuration file to identify a first set of routing rules from a plurality of sets of routing rules.

3. The system of claim 2, wherein the gateway utilizes the first set of routing rules to parse the data request to determine the context for routing the data request to the first application server.

4. The system of claim 1, wherein the operations further comprise rewriting the data request prior to the routing of the data request using an optimization algorithm to create an optimized search pattern based on contents of the data request.

5. The system of claim 1, wherein the operations further comprise selecting the gateway to handle the network traffic based on a current load of each of the plurality of gateways.

6. The system of claim 1, wherein the operations further comprise using a configuration file having information pertaining to the routing of the data request.

7. The system of claim 6, wherein the operations further comprise checking for a new configuration file by periodically polling a configurator coupled to a configuration database storing one or more configuration files.

8. The system of claim 1, wherein the operations further comprise:

mapping a user host identification associated with the data request to the first application server; and

identifying the first application server using the user host identification.

9. The system of claim 1, wherein the operations further comprise routing based on the context of the data request not corresponding to data stored at the database.

10. A method comprising:

receiving network traffic from a plurality of external-facing load balancers at a gateway of a distributed network application, the distributed network application including the plurality of external-facing load balancers, a plurality of gateways including the gateway, a plurality of internal-facing load balancers, a plurality of application servers, and a database, the plurality of gateways located between the plurality of external-facing load balancers and the plurality of internal-facing load balancers, the network traffic including one or more data requests;

inspecting, using one or more hardware processors of the gateway, a data request of the one or more data requests to determine a context of the data request;

routing the network traffic from the plurality of external-facing load balancers to the gateway based on a geographic location of an origin of the network traffic; and

routing, based on the context of the data request corresponding to data stored at the database, the data request from the gateway to a first internal-facing load balancer of the plurality of internal-facing load balancers associated with a first application server of the plurality of application servers based on at least geographic proximity of the first application server to the database.

11. The method of claim 10, wherein the gateway includes a configuration file, wherein the gateway utilizes the configuration file to identify a first set of routing rules from a plurality of sets of routing rules.

12. The method of claim 11, wherein the gateway utilizes the first set of routing rules to parse the data request to determine the context for routing the data request to the first application server.

13. The method of claim 10, further comprising rewriting the data request prior to the routing of the data request using an optimization algorithm to create an optimized search pattern based on contents of the data request.

14. The method of claim 10, further comprising selecting the gateway to handle the network traffic based on a current load of each of the plurality of gateways.

15. The method of claim 10, further comprising using a configuration file having information pertaining to the routing of the data request.

16. The method of claim 15, further comprising checking for a new configuration file by periodically polling a configurator coupled to a configuration database storing one or more configuration files.

17. The method of claim 10, further comprising:

mapping a user host identification associated with the data request to the first application server; and

identifying the first application server using the user host identification.

18. The method of claim 10, further comprising routing based on the context of the data request not corresponding to data stored at the database.

19. A machine-readable storage medium having no transitory signals and embodying instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

receiving network traffic from a plurality of external-facing load balancers at a gateway of a distributed network application, the distributed network application including the plurality of external-facing load balancers, a plurality of gateways including the gateway, a plurality of internal-facing load balancers, a plurality of application servers, and a database, the plurality of gateways located between the plurality of external-facing load balancers and the plurality of internal-facing load balancers, the network traffic including one or more data requests;

inspecting, using one or more hardware processors of the gateway, a data request of the one or more data requests to determine a context of the data request;

routing the network traffic from the plurality of external-facing load balancers to the gateway based on a geographic location of an origin of the network traffic; and

routing, based on the context of the data request corresponding to data stored at the database, the data request from the gateway to a first internal-facing load balancer of the plurality of internal-facing load balancers associated with a first application server of the plurality of application servers based on at least geographic proximity of the first application server to the database.

20. The non-transitory machine-readable storage medium of claim 19, wherein the gateway includes a configuration file, wherein the gateway utilizes the configuration file to identify a first set of routing rules from a plurality of sets of routing rules.