Distributed application definition

• US 9,778,915 B2
• Filed: 02/28/2011
• Issued: 10/03/2017
• Est. Priority Date: 02/28/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): COYER, RYAN D
• Application Number:
  US13/037,299
• Publication Number:
  US 20120222003A1
• Time in Patent Office: 2,409 Days
• Field of Search: 717104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design

Abstract

A method of creating an application definition for a distributed application is disclosed. Constructs corresponding with a schema of the distributed application are defined in a declarative and technology agnostic manner. The constructs include the application definition, a module definition, and a component definition. Each construct includes metadata.

Claims

1. A method of creating an application definition for a distributed application, comprising:

declaratively defining a plurality of constructs corresponding with a schema of the distributed application in a technology agnostic manner, the distributed application including one or more modules, and the one or more modules include, respectively, one or more components;

wherein the constructs include the application definition, a module definition, and a component definition, wherein the constructs include metadata, respectively; and

declaratively defining in metadata an amount of module instances and an amount of partitions assigned to the module instances, respectively, to be activated at runtime;

wherein at runtime, an application framework provides the connections between the components, and wherein at runtime the application definition is used by the application framework to validate a compositional structure of the distributed application.

2. The method of claim 1 wherein the application definition includes a plurality of module definitions and the module definitions include a plurality of component definitions, respectively.

3. The method of claim 2 wherein the module definitions include a common set of metadata shared in the module definitions, respectively.

4. The method of claim 3 wherein the common set of metadata includes metadata regarding “

Name,”

“

Qualified Name,”

“

Isolation Level,”

“

Machine Size,”

“

Enable High Availability,”

“

Instance Count Hint,”

“

Component Definitions,” and

“

Aspect Definitions.”

5. The method of claim 2 wherein the component definitions include a common set of metadata shared in the module definitions, respectively.

6. The method of claim 5 wherein the common set of metadata includes metadata regarding “

Component Name,”

“

Qualified Name,”

“

Version,”

“

Activation Policy,”

“

Module Affinity,”

“

Component Type,” and

“

Artifacts.”

7. The method of claim 1 and further comprising serializing the application definition.

8. The method of claim 7 wherein the application definition is serialized from a scripting language.

9. The method of claim 1 and further comprising including the application definition within an application manifest.

10. The method of claim 1 wherein the application definition is used through an application lifecycle.

11. The method of claim 1 wherein the constructs include a component export definition, a component import definition and a component aspect definition.

12. The method of claim 11 wherein the component export definition includes metadata regarding “

Name,”

“

Qualified Name,”

“

Exporting Component Name,”

“

Proxy Artifacts,”

“

Proxy Type Hint,”

“

Aspects,”

“

Contract,”

“

Visibility,”

“

Listen Address,”

“

Claimed Listen Address Hint,”

“

Canonical Address,” and

“

Publish Address.”

13. The method of claim 11 wherein the component import definition includes metadata regarding “

Name,”

“

Qualified Name,”

“

Owner Component,”

“

Instancing Policy,”

“

Cardinality,” and

“

Constraint.”

14. The method of claim 11 wherein the component aspect definition includes metadata regarding “

Name,”

“

Qualified Name,”

“

Before Advice Pointcut Predicate,”

“

After Advice Pointcut Predicate,”

“

Error Advice Pointcut Predicate,”

“

Final Advice Pointcut Predicate,”

“

Around Advice Pointcut Predicate,”

“

Artifacts,” and

“

Component Aspect Type.”

15. The method of claim 1 wherein the application definition includes metadata regarding “

Name,”

“

Base URI [universal resource identifier],”

“

ID [identifier],”

“

Version,”

“

Base Path,”

“

Module Definitions,”

“

Aspect Definitions,”

“

External Exports,” and

“

Tenant.”

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

creating an application definition for a distributed application described in a schema, the distributed application including one or more modules, and the one or more modules include, respectively, one or more components, wherein the application definition includes a plurality of constructs corresponding with a schema of the distributed application, wherein creating the application definition includes;

expressing component configurations and constraints within the constructs in a declarative manner; and

expressing component dependencies, interrelationships, and interactions within the constructs in a declarative manner;

wherein the constructs include metadata in a technology agnostic format; and

adjustably programming the metadata to declaratively define an amount of module instances and an amount of partitions assigned to the module instances, respectively, to be assigned at runtime;

wherein at runtime, an application framework provides the connections between the components, and wherein at runtime the application definition is used by the application framework to validate a compositional structure of the distributed application.

17. The computer readable storage medium of claim 16 and further comprising serializing the application definition.

18. The computer readable storage medium of claim 16 and further including applying the application definition to validate a compositional structure of the distributed application.

19. The computer readable storage medium of claim 18 and further including applying the application definition to enforce the compositional structure at runtime.

20. A method of creating an application definition for a distributed application, comprising:

declaratively defining a plurality of constructs corresponding with a schema of the distributed application in a technology agnostic manner, wherein the schema includes one or more modules and the one or more modules include, respectively, one or more components;

wherein the constructs include the application definition, a module definition for the one or more modules, respectively, a component definition for the one or more components, respectively, a component export definition for the one or more components providing an export, respectively, a component import definition for the one or more components using an import, respectively, and a component aspect definition;

wherein the constructs include metadata; and

adjustably programming the metadata to declaratively define an amount of module instances and an amount of partitions assigned to the module instances, respectively, to be assigned at runtime;

wherein at runtime, an application framework provides the connections between the components, wherein at runtime the application definition is used by the application framework to validate and enforce a compositional structure of the distributed application.

21. A system for creating an application definition for a distributed application in an application framework, the system comprising:

a processor; and

memory comprising instructions executable by the processor to;

declaratively define a plurality of constructs to correspond with a schema of the distributed application in a technology agnostic manner, the distributed application includes one or more modules, and the one or more modules include, respectively, one or more components,

the plurality of constructs include an application definition, a module definition, and a component definition corresponding with one or more module instances of the schema of the distributed application, the one or more module instance having a plurality of components according to the component definition, and the constructs include metadata;

declaratively define in metadata in the module definition an amount of module instances and an amount of partitions assigned to the module instances to be activated at runtime;

provide the connections between the components at runtime with the application framework; and

validate a compositional structure of the distributed application with the application definition used by the application framework.

22. The system of claim 21 wherein declaratively define in metadata includes adjustably program the metadata to declaratively define an amount of module instances to be assigned at runtime.

23. The system of claim 21 wherein the memory comprises instructions executable by the processor to enforce the compositional structure of the distributed application.

24. The system of claim 21 wherein the memory comprises instructions executable by the processor to serialize the application definition.

25. The system of claim 21 wherein the memory comprises instructions executable by the processor to declaratively define a component export definition, a component import definition, and a component aspect definition.