Pattern-Based Development and Management of Cloud Applications

Abstract

Cloud-based applications require a high degree of automation regarding their IT resource management, for example, to handle scalability or resource failures. This automation is enabled by cloud providers offering management interfaces accessed by applications without human interaction. The properties of clouds, especially pay-per-use billing and low availability of individual resources, demand such a timely system management. We call the automated steps to perform one of these management tasks a “management flow”. Because the emerging behavior of the overall system is comprised of many such management flows and is often hard to predict, we propose defining abstract management flows, describing common steps handling the management tasks. These abstract management flows may then be refined for each individual use case. We cover abstract management flows describing how to make an application elastic, resilient regarding IT resource failure, and how to move application components between different runtime environments. The requirements of these management flows for handled applications are expressed using architectural patterns that have to be implemented by the applications. These dependencies result in abstract management flows being interrelated with architectural patterns in a uniform pattern catalog. We propose a method by use of a catalog to guide application managers during the refinement of abstract management flows at the design stage of an application. Following this method, runtime-specific management functionality and management interfaces are used to obtain automated management flows for a developed application

Model-driven integration for a service placement optimizer in a sustainable cloud of clouds

“…CCPs are proposed as a catalogue of architectural patterns in a natural language [13]. No tools have implemented them.…”

“…The MDI framework consists of (1) a metamodel to graphically define integration models for federated clouds and (2) an MDI tool that accepts an integration model defined with the proposed metamodel and transforms it to integration code (e.g., program code and deployment configurations). The proposed metamodel allows cloud integrators to describe and maintain inter-cloud integration solutions as graphical models using Enterprise Integration Patterns (EIPs) [12] and Cloud Computing Patterns (CCPs) [13]. With the proposed EIP-CCP metamodel, intercloud integration solutions can be modeled at a high-level of abstraction without depending on any particular low-level implementation, deployment and integration technologies.…”

“…They capture best practices in system integration and provide a common integration terminology and modeling notation. Cloud Computing Patterns (CCPs) are architectural patterns to describe cloud types, cloud service models, cloud offerings and cloud application architectures in an abstract form [13].…”

Error Isolation and Management in Agile Multi-Tenant Cloud Based Applications

“…Some versions of this and related problems have been studied in [2] and [5]. Similarly, significant work has been done in the closely related field of logging [6].…”

Is It True for Static Scaling Cloud Model there Exists a Centrally Asymmetric Static Workload Pattern?

“…In our view, one of its most natural refinements is the concept of actual quantifiability. Actual quantifiability is based on the following two conditions: The first states that cloud service providers are cautious [2] [8] [10] [22], meaning that they do not exclude any cloud consumers' static workload resource pooling pattern choice from consideration. The second condition states that whenever premise that a static workload resource pooling pattern choice is better than another static workload resource pooling pattern choice for a cloud consumer, then the probability assign to must be at most times the probability assign to .…”