Identifying Cloud computing usage patterns

Abstract

The current end-users who are developing Cloudbased applications are struggling with multiple solutions for application programming interfaces (APIs) coming from different providers. This fact is partially a consequence of the focus of these APIs on the service provider expectations not on the end-user requirements.In the design of a generic API for Cloud application development, the first step should be the identification of the current Cloud computing use cases. The next step should be the identification of some patterns in these use cases that will be finally exposed to the developers as blocks (templates of the API) for building complex Cloud-based applications.This paper describes the aims of a generic API for Cloud-based applications, discuss the existing Cloud use cases, and exposes the design of a collection of Cloud usage patterns.

Towards a Service Friendly Cloud Ecosystem

“…The architecture of the platform has been designed around the use of open and standard interfaces [13] and through several use cases presented in [14], [15] and [16]. Its main goal is to provide a unified Cloud programming interface which enables the flexibility needed to build inter-operable applications across different Cloud providers [17], and is comprised of the mOSAIC API and the Cloud Agency.…”

Non-functional data layer patterns for Cloud applications

“…Petcu [20] proposes Cloud usage patterns for Cloudbased applications based on existing use cases. Fehling et al [21] and Pallmann [22] provide high-level architectural patterns to design, build, and manage applications using Cloud services.…”

Table of Figures

“…Most cloud patterns like Proxy Service, message queue or Composed Service were adopted from SOA or parallel computing [9]. These patterns were refined to take into account the specificities and requirements of the cloud.…”