Bigtable: a distributed storage system for structured data
OSDI '06 Proceedings of the 7th USENIX Symposium on Operating Systems Design and Implementation - Volume 7
netWorker - Cloud computing: PC functions move onto the web
Aneka: Next-Generation Enterprise Grid Platform for e-Science and e-Business Applications
E-SCIENCE '07 Proceedings of the Third IEEE International Conference on e-Science and Grid Computing
Turning Software into a Service
Computer
IT Professional
IEEE Internet Computing
A Cloud Oriented Approach for People-Provided Services
ICIW '10 Proceedings of the 2010 Fifth International Conference on Internet and Web Applications and Services
CCGRID '10 Proceedings of the 2010 10th IEEE/ACM International Conference on Cluster, Cloud and Grid Computing
Cloud Computing: The New Frontier of Internet Computing
IEEE Internet Computing
COSCA: an easy-to-use component-based PaaS cloud system for common applications
Proceedings of the First International Workshop on Cloud Computing Platforms
Cloud Computing Standards: Where's the Beef?
IEEE Internet Computing
Program Ultra-Dispatcher for launching applications in a customization manner on cloud computing
Journal of Network and Computer Applications
SP 800-145. The NIST Definition of Cloud Computing
SP 800-145. The NIST Definition of Cloud Computing
Hi-index | 0.00 |
Traditional cloud computing providers enable developers to program and deploy applications in the cloud by using platform as a service (PaaS) providers. Despite the benefits of such an approach, this service model usually comes with a high level of the lock in effect into the service provider. The lock in effect occurs when a software developer needs to change its cloud provider. When this happens, it usually means a major application rewrite, specific for the new PaaS. This paper details the initial results of a project whose goal is to build a PaaS where vendor lock in does not occur. With this PaaS, developers wishing to deploy their applications into the cloud may continue to program using their usual development environments. There are no necessary changes required to make the application PaaS compatible. As a proof of concept, we developed an open source PaaS management application as a regular web application and then deployed it on the cloud.