ROUTING TRAFFIC IN AN ONLINE SERVICE WITH HIGH AVAILABILITY

• US 20120102220A1
• Filed: 10/20/2010
• Published: 04/26/2012
• Est. Priority Date: 10/20/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hopmann, Alexander, Fox, Eric, Furtwangler, Tyler
• Application Number:
  US12/908,724
• Publication Number:
  US 20120102220A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Web request routers in a cloud management system are used to route requests to content within the networks that are associated with an online service. The web request routers receive requests, parse the requests and forward the requests to the appropriate destination. The web request routers may use application specific logic for routing the requests. For example, the requests may be routed based on a document identifier and/or user information that is included within the received request. A look up table may be used in determining a destination for the request. When a location of content changes within the online service, the look up table may be updated such that the web request routers automatically direct content to the updated location. A user may also specify where their requests are to be routed.

Claims

1. A method for routing requests in an online service, comprising:

receiving a request for content in a network of the online service;

wherein the request is received by a load balancer in the network for the online service that routes the request to a web request router in a group of web request routers in the online service to determine a destination of the content;

parsing the request;

determining a destination of the request using application specific information that is stored within the request; and

forwarding the request to the destination.

2. The method of claim 1, wherein determining the destination comprises accessing a look up table that contains a list of destinations.

3. The method of claim 1, wherein parsing the request comprises determining a document name that is included within the received request.

4. The method of claim 1, wherein parsing the request comprises determining at least one of:

an application from the request for which the content is associated;

a version of an application from the request for which the content is associated.

5. The method of claim 1, wherein determining the destination of the request using the application information that is stored within the request comprises determining a customer that is associated with the request.

6. The method of claim 1, wherein a request for a same document is processed by a server that handles each of the requests for a specific document.

7. The method of claim 2, further comprising using a caching server to store the look up table.

8. The method of claim 2, further comprising determining when the request is a non-user initiated request and determining when a request is a replicated request.

9. The method of claim 2, further comprising allowing a user to update the look up table to specify the destination for requests that are received from a tenant.

10. A computer-readable storage medium having computer-executable instructions for routing requests in an online service, comprising:

receiving a request for content in a network of the online service;

wherein the request is received by a load balancer in the network for the online service that routes the request to a web request router in a group of web request routers in the online service to determine a destination of the content;

parsing the request;

determining a destination of the request using application specific information that is stored within the request; and

forwarding the request to the destination.

11. The computer-readable storage medium of claim 10, wherein determining the destination comprises accessing a look up table that contains a list of destinations that is accessed by each of the web request routers when determining the destination.

12. The computer-readable storage medium of claim 10, wherein parsing the request comprises determining a document name that is included within the received request.

13. The computer-readable storage medium of claim 10, wherein parsing the request comprises determining an application and a customer from the request for which the content is associated.

14. The computer-readable storage medium of claim 10, wherein determining the destination comprises selecting a same destination for each document request that is the same.

15. The computer-readable storage medium of claim 11, further comprising automatically updating the look up table in response to content being moved to a new machine.

16. The computer-readable storage medium of claim 11, further comprising allowing a user to update the look up table through an Application Programming Interface to specify the destination for requests that are received from a tenant.

17. A system for routing requests in an online service, comprising:

a processor and a computer-readable medium;

an operating environment stored on the computer-readable medium and executing on the processor;

a cloud manager that is coupled to different networks that is operative to manage deployment of machines and configuration of the networks in the online service; and

web request routers that are each configured to perform actions, comprising;

receive a request for content in the online service;

parse the request;

determine a destination of the request using application specific information that is stored within the request;

wherein the application specific information comprise a name of a document; and

forwarding the request to the destination.

18. The system of claim 17, wherein determining the destination comprises accessing a look up table that contains a list of destinations that is accessed by each of the web request routers when determining the destination.

19. The system of claim 17, wherein the web request routers are configured to route cross network and cross data center.

20. The system of claim 18, further comprising allowing a user to update the look up table through an Application Programming Interface to specify the destination for requests that are received from a tenant.