Stateful component authoring and execution

• US 9,465,589 B2
• Filed: 04/05/2011
• Issued: 10/11/2016
• Est. Priority Date: 04/05/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Shukla, Dharma, Sagar, Akash Jeevan, Talbert, Nathan C., Annamalai, Muthukaruppan, Schmidt, Robert B., Bhandarkar, Aditya, Jawahar, Asad
• Primary Examiner(s): Kang, Insun
• Application Number:
  US13/080,369
• Publication Number:
  US 20120260227A1
• Time in Patent Office: 2,016 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/35 model driven

Abstract

A method for of authoring and executing stateful components for a distributed application is disclosed. An application schema for the distributed application is declaratively defined and includes a plurality of distributed modules. Each module hosts a set of stateful components co-located in a physical tier of a distributed environment having logic to manipulate state. The runtime supports partitioning the stateful components. Control flow opaqueness of component logic is banished in each of the stateful components, which would otherwise occur if state was externalized.

Claims

1. A method of authoring and executing stateful components for a distributed application, the method comprising:

declaratively defining an application schema for the distributed application including a plurality of distributed modules, wherein each module hosts a set of stateful components in a physical tier of a distributed environment having logic to manipulate state, and wherein the application schema includes a serialized and programmable module definition corresponding with each module, wherein each module definition includes declaratively defined associated metadata to describe the aspects of the module; and

providing runtime support of selectively partitioning the stateful components into scalable partitions, each partition includes a state of the partition of the stateful component co-located with logic to manipulate state without externalizing state from state logic, in response to adjustably programming the associated metadata to declaratively define an amount of module instances, an amount of partitions assigned to each module instance, and an amount of replicas for each partition to be created at runtime.

2. The method of claim 1 wherein the partitions are atomic.

3. The method of claim 1 wherein the partitions are mutually exclusive.

4. The method of claim 1 wherein the partitions are units of load balancing.

5. The method of claim 1 wherein a partition includes a backup replica.

6. The method of claim 5 wherein the backup replica is located on another physical tier.

7. The method of claim 1 wherein the stateful components provide a service, and clients address the service with a logical address.

8. The method of claim 7 wherein the logical address is resolved into a physical address at the client at runtime.

9. The method of claim 1 wherein control flow opaqueness occurs when state is externalized.

10. The method of claim 1 wherein the partitions are independent of each other and each partition receives a corresponding application domain.

11. The method of claim 1 wherein the application schema includes stateless components, wherein the stateless components are scaled with cloning.

12. The method of claim 1 wherein the stateful components are exclusive of components that externalize state.

13. The method of claim 12 wherein each statelful component includes an output of a request to the component that is a function of an input and data materialized in context of a previous request to the component.

14. The method of claim 1 wherein object-relational mapping is integrated with the stateful components.

15. The method of claim 1 comprising:

banishing control flow opaqueness of component logic in each of the stateful components.

16. A computer readable storage medium, which does not include transitory propagating signals, storing computer executable instructions for controlling a computing device to perform a method comprising:

providing an extensible framework for authoring and executing stateful components for a distributed application, wherein the providing comprises;

declaratively defining abstractions in an application schema for the distributed application including a plurality of distributed modules, wherein each module hosts a set of stateful components in a physical tier of a distributed environment having logic to manipulate state, and wherein the application schema includes a serialized and programmable module definition corresponding with each module, wherein each module definition includes declaratively defined associated metadata to describe the aspects of the module; and

providing runtime support of selectively partitioning the stateful components into scalable partitions, each partition includes a state of the partition of the stateful component co-located with logic to manipulate state without externalizing state from state logic, in response to adjustably programming the associated metadata to declaratively define an amount of module instances, an amount of partitions assigned to each module instance, and an amount of replicas for each partition to be created at runtime.

17. The computer readable storage medium of claim 16 wherein the plurality of distributed modules provide partition-aware routing.

18. The computer readable storage medium of claim 17 wherein the distributed application includes metadata regarding instance count.

19. The computer readable storage medium of claim 18 wherein the distributed application includes metadata regarding a partitioning policy and a replica count.

20. A method of authoring and executing stateful components for a distributed application, the method comprising:

providing an extensible framework for authoring and executing stateful components for a distributed application, wherein the providing comprises;

declaratively defining abstractions in an application schema for the distributed application including a plurality of distributed modules, wherein each module hosts a set of stateful components co-located in a physical tier of a distributed environment having logic to manipulate state, and wherein the application schema includes a serialized and programmable module definition corresponding with each module, wherein each module definition includes declaratively defined associated metadata to describe the aspects of the module; and

providing runtime support of selectively partitioning the stateful components into scalable partitions according to definition constructs corresponding with the distributed modules, each partition includes a state of the partition of the stateful component co-located with logic to manipulate state without externalizing state from state logic, in response to adjustably programming the associated metadata to declaratively define an amount of module instances, an amount of partitions assigned to each module instance, and an amount of replicas for each partition to be created at runtime.

21. A system for authoring and executing stateful components for a disturbed application, the system comprising:

a computing device including a processor and a memory configured to;

declaratively define an application schema for the distributed application including a plurality of distributed modules, each module hosts a set of stateful components in a physical tier of a distributed environment having logic to manipulate state, the application schema includes a serialized and programmable module definition corresponding with each module, each module definition includes declaratively defined associated metadata to described the aspects of the module; and

provide runtime support of selectively partitioning the stateful components into scalable partitions, each partition includes a state of the partition of the stateful component co-located with logic to manipulate state without externalizing state from state logic, in response to adjustably programming the associated metadata to declaratively define an amount of module instances, an amount of partitions assigned to each module instance, and an amount of replicas for each partition to be created at runtime.

22. The system of claim 21 wherein the plurality of distributed modules provide partition-aware routing.

23. The system of claim 21 wherein computing device is configured to:

address the stateful components with a logical address, the logical address is resolved into a physical address at runtime.

24. The system of claim 21 wherein the application schema includes stateless components and the stateless components are scaled with cloning.

25. The system of claim 21 wherein the partitions are independent of each other and each partition receives a corresponding application domain.