Automated deployment of defined topology in distributed computing environment

A computer program product comprising a non-transitory computer usable storage medium embodying computer usable program code for deploying a software product comprising a plurality of components comprising:

• computer usable program code, stored in at least one non-transitory storage medium, for reading a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a dependency includes at least a must-access dependency and a realization dependency, wherein a must-access dependency states that a component must have access to a particular publisher, and a realization dependency is used to derive concrete components for conceptual ones;
• computer usable program code, stored in at least one non-transitory storage medium, for reading characteristics of a plurality of publishers;
• computer usable program code, stored in at least one non-transitory storage medium, for matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers;
• computer usable program code, stored in at least one non-transitory storage medium, for distributing the plurality of components among the plurality of publishers responsive to the computer usable program code for matching;
• and
• computer usable program code, stored in at least one non-transitory storage medium, for validating each set of components distributed to each publisher comprises:
• confirming, using feedback from the publisher, that the set of components can compile and execute on the corresponding publisher.

A server for deploying a software product comprising a plurality of components, comprising:

• a data repository for storing a topological description of the software product and its components, wherein the topological description defines characteristics and dependencies of the components, and wherein a dependency includes at least a must-access dependency and a realization dependency, wherein a must-access dependency states that a component must have access to a particular publisher, and a realization dependency is used to derive concrete components for conceptual ones, and for storing characteristics of a plurality of publishers;
• a processor configured for matching each of the plurality of components to one of the plurality of publishers according to the characteristics and dependencies of the components and the characteristics of the plurality of publishers;
• a transmitter for distributing the plurality of components among the plurality of publishers responsive to the step of matching;
• and
• a receiver for validating each set of components distributed to each publisher comprises:
• confirming, using feedback from the publisher, that the set of components can compile and execute on the corresponding publisher.