Standardization in Cloud Computing

Title: Standardization in Cloud Computing
Publisher: Guru Nanak Publications
ISSN: 2278-0947
Series: Volume 5 Issue 1
Authors: N. Leelavathy, Ch. Sowmya, Ch. Sushmitha


Abstract

Much attention has been given to data sharing services utilizing a cloud computing environment. Cloud compu-ting is a computing technology to provide IT resources (e.g., software, storage, and server) with internet tech-nology. Everybody talks about it but with little know-ledge of the implications. Cloud computing has become very useful because of its cost effectiveness, high availability, anywhere access, and infinitely scalable. There are a lot of vendors including Microsoft, IBM, Amazon, and Google providing cloud services. A currently recurring issue in the context of commercial cloud is "vendor lock in": As most commercial tools were developed independently from one another with a particular focus on solving the respective company's customers' prob-lems first, there is little (technical) convergence between the available products. This is also due to the typical development cycle of clouds which typically start as in-house, internal solutions (private clouds) which are then extended to provide (a subset of) capabilities to potential customers (public clouds). There are no standards as such in the cloud computing discipline. Each vendor has his own standards, which are not compatible with others. This results in vendor lock-in and it has become very difficult for the customer to change the Cloud vendor whenever needed. This situation is similar to the DBMS before ODBC. We need a technique similar to ODBC in cloud computing, so that the client can mi-grate among cloud vendors without redesigning and recompiling massive systems and also without converting the data. This paper discusses the need for such standard and proposes a conceptual standard for the cloud computing discipline.

Keywords

Cloud, Interoperability, Vendor Lock-in, Java Database Connectivity, mixins.

Download Full Text

(For complimentary copy, please contact Chief_editor@innovationjournals.com)