System and method for managing network traffic routing

Patent metadata

Field	Value
Publication number	US-9953097-B2
Application number	US-68751807-A
Country	US
Kind code	B2
Filing date	Mar 16, 2007
Priority date	Mar 16, 2006
Publication date	Apr 24, 2018
Grant date	Apr 24, 2018

Abstract

A method and system receives at a server a search request and processes the search request to determine a context of the search request, then determines, based on the context, a network route to an application server having the closest geographic proximity, with respect to the server, to the most relevant database associated with the context.

First claim

We claim:

1. A method, including:
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 plurality of databases, the plurality of gateways located between the plurality of external-facing load balancers and the plurality 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, based on the context of the data request corresponding to data stored at a database of the plurality of databases, 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 having a closest geographic proximity to the database; and
routing, based on the context of the data request not corresponding to data stored at any database of the plurality of databases, the data request from the gateway to a second internal-facing load balancer of the plurality of load balancers associated with a second application server of the plurality of application servers having a closest geographic proximity to the gateway.

2. The method according to claim 1 , further including 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.

3. The method according to claim 1 , further including selecting the gateway to handle the network traffic based on a current load of each of the plurality of gateways.

4. The method according to claim 1 , further including using a configuration file having information pertaining to the routing of the data request.

5. The method according to claim 4 , further including checking for a new configuration file by periodically polling a configurator coupled to a configuration database storing one or more configuration files.

6. The method according to claim 1 , further including:
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.

7. The method according to claim 1 , further including 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.

8. A method, including:
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 plurality of databases, 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 uniform resource locators (URLs);
parsing, using one or more hardware processors of the gateway, a URL of the one or more URLs to determine a context of a data request associated with the URL;
routing, based on the context of the data request corresponding to data stored at a database of the plurality of databases, 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 having a closest geographic proximity to the database; and
routing, based on the context of the data request not corresponding to data stored at any database of the plurality of databases, the data request from the gateway to a second internal-facing load balancer of the plurality of internal-facing load balancers associated with a second application server of the plurality of application servers having a closest geographic proximity to the gateway.

9. A system, comprising:
one or more processors;
memory including instructions that, when executed by the one or more processors, cause the system to:
receive 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 system, a plurality of internal-facing load balancers, a plurality of application servers, and a plurality of databases, 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;
inspect a data request of the one or more data requests to determine a context of the data request;
route, based on the context of the data request corresponding to data stored at a database of the plurality of databases, the data request 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 having a closest geographic proximity to the database; and
route, based on the context of the data request not corresponding to data stored at any database of the plurality of databases, the data request to a second internal-facing load balancer of the plurality of load balancers associated with a second application server of the plurality of application servers having a closest geographic proximity to the system.

10. The system according to claim 9 , wherein the instructions when executed further cause the system to rewrite 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.

11. The system according to claim 9 , wherein the instructions when executed further cause the system to select the system to handle the network traffic based on a current load of each of the plurality of gateways.

12. The system according to claim 9 , wherein the instructions when executed further cause the system to use a configuration file that includes information pertaining to the routing of the data request.

13. The system according to claim 12 , wherein the instructions when executed further cause the system to check for a new configuration file by periodically polling a configurator coupled to a configuration database storing one or more configuration files.

14. The system according to claim 9 , wherein the instructions when executed further cause the system to:
map a user host identification associated with the data request to the first application server; and
identify the first application server using the user host identification.

15. The system according to claim 9 , wherein the instructions when executed further cause the system to route 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.

16. A non-transitory machine-readable storage medium 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

Assignees

• Pritchett Dan L
• Flint Ian
• Yang Connie Y
• Ebay Inc

Inventors

• Pritchett Dan L
• Flint Ian
• Yang Connie Y

Classifications

• H04L29/12594

  Electricity · mapped topic

• H04L61/30

  Managing network names, e.g. use of aliases or nicknames (name-to-address mapping H04L61/45) · CPC title

• H04L67/1002

  Electricity · mapped topic

• H04L67/1021

  based on client or server locations · CPC title

• H04L61/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 title