The cloud computing paradigm has achieved widespread adoption in recent years. Its success is due largely to customers’ ability to use services on demand with a pay-as-you go pricing model, which has proved convenient in many respects. Low costs and high flexibility make migrating to the cloud compelling. Despite its obvious advantages, however, many companies hesitate to “move to the cloud,” mainly because of concerns related to service availability, data lock-in, and legal uncertainties.1 Lockin is particularly problematic. Public cloud providers generally don’t guarantee particular service level agreements. Public cloud providers’ terms of service let that provider unilaterally change pricing at any time. Myriad cloud providers are f looding the market with a confusing body of services, including compute services such as the Amazon Elastic Compute Cloud (EC2) and VMware vCloud, or key-value stores, such as the Amazon Simple Storage Service (S3). Some of these services are conceptually comparable to each other, whereas others are vastly different, but they’re all, ultimately, technically incompat ible and fol low no standards but their own. This meta cloud would abstract away from existing offerings’ technical incompatibilities, thus mitigating vendor lock-in. Request handlers place bet records in a message queue and subsequently store them in a relational database. the automated formation and provisioning of cloud applications also depends on sophisticated features to actually deploy and install applications automatically. Various vendors provide tools for cloud monitoring, ranging from system-level monitoring (such as CPU and bandwith) to application-level monitoring.
You are here: Home / ieee projects 2013 / Amazon’s Cloud Formation upcoming the meta cloud for TOSCA specification