Composition model for cloud-hosted serving applications

• US 9,229,980 B2
• Filed: 02/23/2010
• Issued: 01/05/2016
• Est. Priority Date: 02/23/2010
• Status: Active Grant

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Feng, Andrew An, Makeev, Evgeniy, Budzinski, Jeffrey, Lim, Swee, Banachowski, Scott Alexander, Stata, Raymond Paul, Chandra, Rohit
• Primary Examiner(s): KIM, DONG U
• Application Number:
  US12/711,146
• Publication Number:
  US 20110209007A1
• Time in Patent Office: 2,142 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 16/24542 Plan optimisation

Abstract

Methods and apparatus for executing an application are disclosed. In accordance with one embodiment, a request is received. One or more of a plurality of module types are instantiated such that a plurality of module objects are generated. A query plan linking the plurality of module objects is executed such that a response to the request is generated. The response is then returned.

Claims

1. A method, comprising:

instantiating a plurality of module types such that a plurality of module objects are generated, wherein the plurality of module types include a request module type and a response module type, wherein each of the plurality of module objects is defined by a corresponding interface definition, wherein the plurality of module types are different classes;

instantiating, by middleware, a query plan linking the plurality of module objects, wherein the plurality of module objects includes an instance of the request module type and an instance of the response module type;

receiving, at the middleware from a horizontal container, a request, wherein the horizontal container provides a context object to the middleware to be passed between the plurality of module objects during execution of the query plan;

receiving, at the middleware from the horizontal container, abstract endpoints corresponding to endpoints in a cloud;

executing, by the middleware, the query plan linking the plurality of module objects such that a response to the request is generated, wherein the instance of the request module type processes the request and wherein the response is formed by the instance of the response module type, wherein the middleware communicates with the endpoints in the cloud via the abstract endpoints; and

returning, by the middleware, the response to the horizontal container.

2. The method as recited in claim 1, wherein the plurality of module types further include an asynchronous module type such that the plurality of module objects include an asynchronous module, wherein the asynchronous module type invokes a network service, wherein the asynchronous module includes a callback method that is called by the horizontal container when a response is received from the network service.

3. The method as recited in claim 1, wherein the plurality of module types further includes a branch module type or a multibranch module type, wherein the branch module type determines one of two or more child modules to invoke, and wherein the multibranch module type selects one or more branch modules of two or more branch modules to invoke.

4. The method as recited in claim 1, wherein the plurality of module types further includes a fork module type whose child nodes are to be executed in parallel.

5. The method as recited in claim 1, wherein the plurality of module types further includes a join module type that performs synchronization for module objects executing simultaneously on independent execution paths, wherein the module objects are associated with different forks of a multi-branch module.

6. The method as recited in claim 1, wherein the plurality of module types further includes a termination module type that is executed when an error occurs during execution of the query plan.

7. The method as recited in claim 6, wherein the response is an error response.

8. The method as recited in claim 1, wherein the request is a search query.

9. The method as recited in claim 8, wherein the response includes search results.

10. The method as recited in claim 1, wherein the request initiates selection of one of a plurality of advertisements, and wherein the response includes a selected one of the plurality of advertisements.

11. The method as recited in claim 1, wherein the interface definition of each of the plurality of module objects declares one or more methods of the corresponding one of the plurality of module objects.

12. The method as recited in claim 1, wherein the interface definition of each of the plurality of module objects identifies one or more attributes that the corresponding one of the plurality of module objects accesses.

13. The method as recited in claim 1, wherein the query plan is executed via the interface definition of each of the plurality of module objects.

14. The method as recited in claim 1, wherein for each of the plurality of module objects, the interface definition is associated with a corresponding one of the plurality of module types.

15. A method, comprising:

generating, by middleware, one or more query plans by instantiating a plurality of module types such that a plurality of module objects are generated for each of the query plans, wherein the plurality of module types are different classes, wherein each of the plurality of module objects is defined by a corresponding interface definition;

receiving, at the middleware from a horizontal container, a request;

receiving, at the middleware from the horizontal container, abstract endpoints corresponding to endpoints in a cloud;

identifying, by the middleware, one of the query plans to process the request;

executing, by the middleware, the identified query plan such that a response to the request is generated, wherein the horizontal container provides a context object to the middleware to be passed between the plurality of module objects of the query plan during execution of the query plan, wherein the middleware communicates with the endpoints in the cloud via the abstract endpoints; and

returning, by the middleware to the horizontal container, the response.

16. The method as recited in claim 15, wherein the plurality of module types include at least one of a branch module type, a multibranch module type, a fork module type, a join module type, or a termination module type.

17. The method as recited in claim 15, further comprising:

validating input and output dependencies of the plurality of module objects within the query plan based upon the interface definition for each of the plurality of module objects.

18. The method as recited in claim 15, wherein the request is a search query.

19. The method as recited in claim 18, wherein the response includes search results.

20. The method as recited in claim 15, wherein the request initiates selection of one of a plurality of advertisements, and wherein the response includes a selected one of the plurality of advertisements.

21. The method as recited in claim 15, wherein the query plan is associated with a service being requested, wherein identifying one of the query plans to process the request comprises:

identifying a service associated with the request; and

identifying one of the query plans providing the service.

22. The method as recited in claim 15, wherein the request is received via a web server and the response is returned via the web server.

23. The method as recited in claim 15, wherein the request is one of a plurality of requests processed in parallel, wherein each of the plurality of requests is processed within one of a plurality of threads.

24. A system, comprising:

means for instantiating, by middleware, one or more query plans such that each of the query plans links a corresponding plurality of module objects;

means for instantiating a plurality of module types such that a plurality of module objects are generated, wherein each of the plurality of module objects is defined by a corresponding interface definition;

means for receiving, by the middleware, a request from a horizontal container;

means for receiving, by the middleware, abstract endpoints corresponding to endpoints in a cloud;

means for executing, by the middleware, at least one of the query plans linking a corresponding plurality of module objects such that a response to the request is generated, wherein the horizontal container provides a context object to the middleware to be passed between the plurality of module objects during execution of the query plan, wherein the middleware communicates with the endpoints in the cloud via the abstract endpoints; and

means for returning the response by the middleware to the horizontal container.

25. The system of claim 24, further comprising:

means for identifying one of the query plans to execute in order to generate a response to a request.

26. The system of claim 24, wherein the plurality of module types include at least one of a branch module type, a multibranch module type, a fork module type, or a join module type, wherein the plurality of module types are different classes.

27. A system, comprising:

one or more processors; and

one or more memories, wherein the processors and the memories are configured to provide;

middleware configured to generate one or more query plans by instantiating a plurality of module types such that a plurality of module objects are generated for each of the query plans, identify one of the query plans to generate a response to a request, and execute the identified query plan, wherein the plurality of module types are different classes, wherein each of the plurality of module objects is defined by a corresponding interface definition, wherein the identified query plan is executed using the interface definition of each of the plurality of module objects; and

a container configured to receive a request and forward the request to the middleware, and configured to receive a response from the middleware and return the response, wherein the container provides a context object to the middleware to be passed between the plurality of module objects of a query plan during execution of the query plan;

wherein the container is further configured to communicate abstract endpoints to the middleware, where the abstract endpoints are mapped to endpoints in a cloud;

wherein the middleware is further configured to communicate with the abstract endpoints.

28. The system as recited in claim 27, wherein the system further comprises:

a mechanism for communicating one or more endpoints in a cloud to the container.