Portability and Interoperability between Clouds: Challenges and Case Study

Petcu, Dana

doi:10.1007/978-3-642-24755-2_6

Cited by 113 publications

(77 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It also helps administrators to monitor the services and measure their quality. While the project is developing a post-fact adoption standard (Petcu, 2011) with CloudML, a domain-specific modeling language and runtime environment that facilitates the specification of cloud application provisioning, deployment, and adaptation, we argue that each enterprise can build its own language or generation 16 http://www.omg.org/mda/ 17 http://www.modaclouds.eu/ strategy more aligned with their business.…”

Section: Related Workmentioning

confidence: 99%

Supporting Multiple Persistence Models for PaaS Applications using MDE - Issues on Cloud Portability

Silva

Lucrédio

Moreira

et al. 2015

Proceedings of the 5th International Conference on Cloud Computing and Services Science

View full text Add to dashboard Cite

Abstract:In cloud computing, lock-in refers to the difficulty of porting an application from one platform to another. An example of such difficulty can be witnessed when porting an application from Platform-as-a-Service Google App Engine to Microsoft Azure. Differences in their implementations are substantial, yielding non-portable applications. Standardization could address this problem, but existing initiatives are still to be accepted. This paper addresses lock-in by proposing a model-driven engineering design approach that decouples platform specific code from the application logic. The resulting platform-independent models, as well as corresponding model transformations, can be reused to generate distinct platform-specific implementations, hence reducing the programming effort spent coding repetitive tasks. Such transformations can be made available for reuse on a repository for cloud providers. We have implemented transformations to handle persistence for Google App Engine and Azure, and discuss how model-driven engineering can reconcile the differences between features of the persistence models of GAE and Azure.

show abstract

Section: Related Workmentioning

confidence: 99%

Supporting Multiple Persistence Models for PaaS Applications using MDE - Issues on Cloud Portability

Silva

Lucrédio

Moreira

et al. 2015

Proceedings of the 5th International Conference on Cloud Computing and Services Science

View full text Add to dashboard Cite

show abstract

“…For example, developers may decide today to use a PaaS provider for a particular module because it is more cost effective, or because it requires less management effort, but tomorrow they may decide to move some component to IaaS level because their needs or business model may require more control over virtual machines (VM), e.g., for a better integration with their enterprise's infrastructure, or because they need to increase the security level of their services. Unfortunately, moving an application's component between different providers is problematic, and it is more difficult between different abstraction levels, since changes in these decisions require some development efforts [Petcu, 2011, Di Martino, 2014, in order to adapt the components to new service requirements and their integration with other application's components, running in other providers.…”

Section: Introductionmentioning

confidence: 99%

Component-wise Application Migration in Bidimensional Cross-cloud Environments

Carrasco

Durán

Pimentel

2017

Proceedings of the 7th International Conference on Cloud Computing and Services Science

View full text Add to dashboard Cite

Abstract:We propose an algorithm for the migration of cloud applications' components between different providers, possibly changing their service level between IaaS and PaaS. Our solution relies on three of the key ingredients of the trans-cloud approach: a unified API, agnostic topology descriptions, and mechanisms for the independent specification of providers. We show how our approach allows us to overcome some of the current interoperability and portability issues of cloud environments to propose a solution for migration, present an implementation of our proposed solution, and illustrate it with a case study and experimental results.

show abstract

“…Petcu [3] discusses the classical problem of too many different approaches by various vendors in the way they realize the interface to the cloud and offer cloud features.…”

Section: Introductionmentioning

confidence: 99%

An Overview of Cloud Interoperability

Kostoska¹,

Gušev²,

Ristov³

2016

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Unlike the network TCP/IP's and OSI's layered structure of protocols, which allows the independence of protocols of different layers, as well as defining the upper layer protocols through the protocols of the lower layers, the cloud service layers are tightly dependent on each other. For example, an application of the SaaS layer can neither communicate nor exchange data with another application found on the same layer. The goal of this paper is to overview the cloud interoperability and to analyze it as a service model perspective. Several aspects and categories of cloud interoperability are analyzed in this paper.

show abstract

Portability and Interoperability between Clouds: Challenges and Case Study

Cited by 113 publications

References 5 publications

Supporting Multiple Persistence Models for PaaS Applications using MDE - Issues on Cloud Portability

Supporting Multiple Persistence Models for PaaS Applications using MDE - Issues on Cloud Portability

Component-wise Application Migration in Bidimensional Cross-cloud Environments

An Overview of Cloud Interoperability

Contact Info

Product

Resources

About