A Middleware for Managing Non-Functional Requirements in Cloud PaaS

TLDR: This paper introduces an approach enhancing component-based cloud applications with non-functional properties in the context of an integrated programming model that allows developers of such applications to formally declare properties that may influence the application during runtime and document the expectations regarding non- functional aspects of the overall system.

Abstract: A key aspect of distributed applications in platform-as-a-service clouds revolves around the definition of requirements for quality of service and the most efficient use of the available resources to achieve them. Matching both the requirements and resources represents a unique challenge: While requirements are generally defined in relatively abstract form and defined as system-wide parameters, the resources are concrete, low-level entities that, by themselves, are only of marginal influence on the requirements. In order to establish a relationship between these two requires both the agglomeration of properties into more abstract ones as well as refining requirements in more detailed, concrete ones, both of which can often only be done to a certain degree. This paper presents a vision how both aspects can be brought to the same level and introduces an approach enhancing component-based cloud applications with non-functional properties in the context of an integrated programming model. This allows developers of such applications to formally declare properties that may influence the application during runtime and document the expectations regarding non-functional aspects of the overall system. This can be used to ensure the health of the application and, in case requirements are violated, actions like the deployment of additional resources can be performed in order to alleviate any degradation of its non-functional state, either by evaluating, choosing and performing pre-defined actions automatically or by manual administrative intervention.