WINDS OF CHANGE FROM VENDOR LOCK-IN TO THE META CLOUD

Submitted in partial fulfillment of the requirements for the award of the degree of

Bachelor Of Technology
IN
COMPUTER SCIENCE AND ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERIN
SRI SATYANARAYANA ENGINEERING COLLEGE

PRESENTED BY
V.Mounika
Under the estimated guidance of
11X91A0553
K.Pavani
11X91AO521
M.Veera Kumari
11X91A0529
Y.SUSHMA M.Tech
B.Sreeja
11X91A0507
Asst. professor
V.Naveena
11X91A0552

CONTENTS  Abstract  Introduction  Architecture  Existing system  Disadvantages  Proposed system  Advantages  Software requirements  Hardware requirements  Conclusion .

ABSTRACT The cloud computing paradigm has achieved widespread adoption in recent years. and legal uncertainties. many companies hesitate to “move to the cloud.  Lock in is particularly problematic.  . even though public cloud availability is generally high. data lock-in. however.  Despite its obvious advantages. outages still occur.” mainly because of concerns related to service availability.  Low costs and high flexibility make migrating to the cloud compelling.

migrating to a different cloud if they discover problems or if their estimates predict future issues.  This meta cloud would abstract away from existing offerings.INTRODUCTION A need for businesses to permanently monitor the cloud they’re using and be able to rapidly “change horses” that is.  . technical incompatibilities. it helps user find right set of cloud services for a particular use case and supports an application’s initial deployment and run time migration.

.

 . such as the Amazon Simple Storage Service(S3).EXISTING SYSTEM Cloud providers are flooding the market with a confusing body of services. but they’re all.  Some of these services are conceptually comparable to each other. including computer services such as the Amazon Elastic Compute Cloud (EC2) and VMware v Cloud. whereas others are vastly different. ultimately incompatible and follow no standards but their own. or key-value stores.

.  Low costs and high flexibility make migrating to the cloud compelling. which has proved convenient in many aspects.DISADVANTAGES  Its success is due to largely to customers ability to use services on demand with a pay-as-you go pricing model.

. This meta cloud would abstract away from existing offerings technical incompatibilities thus mitigating vendor lock-in. we introduce the concept of a meta cloud that incorporates design time and runtime components. it helps user find the right set of cloud services for a particular use case and supports an application’s initial deployment and runtime migration.PROPOSED SYSTEM  Here.

thus mitigating vendor lock-in .ADVANTAGES  We introduce the concept of a meta cloud that incorporates design time and runtime components.  This meta cloud would abstract away from existing offerings technical incompatibilities.

Tomcat5.0 .My sql .Java Scripts .JDBC .Windows95 .Java .SOFTWARE REQURIMENTS Operating System  Application Server  Front End  Scripts  Database  Database connectivity  .

Pentium-III -1.HARDWARE REQUIREMENTS Processor  Speed  RAM   Hard Disk .1GHz -256 MB (min) -20 GB .

CONCLUSION The meta cloud can help migrate vendor lock-in and promises transparent use of cloud computing services. yet lack integration.  .  Most of the basic technologies necessary to realize the meta cloud already exist.

THANK YOU .