preview

Essay On SLA

Decent Essays

INTRODUCTION
Cloud computing is one of the new models of computing that is used to provide for the computing infrastructure. A good computing cloud data management system must satisfy the following goals like availability, scalability, elasticity, performance [1]. The cloud computing looks to satisfy the needs of various levels of clients and workloads. Hence a guaranteed contract between the service provider and the clients has been made known as the Service Level Agreement (SLA). Both the providers and consumers consider successful SLA management.
OBJECTIVE
The objective is to introduce a SLA based computing database from a consumer’s point of view. In [2] the authors have presented with an end-to-end framework that allows the SLA to be …show more content…

Scaling up involves making use of a bigger machine as the database server and scaling out is focused on replicating the data. To make use of the replicated data the snapshot of the database has to be taken for regular intervals of time. A trade-off occurs between the snapshot time and the size of the lo of transactions.
The SLA-based provisioning in [2] focus on the SLA metrics of the total transaction time more than the throughput of the database. Practically, the requirements of SLA vary between the types of application transactions.
The difference in the SLA is because of the different behaviours of the system resources. The framework helps the service provider to design specific action rules for the application to adapt to the scale in or scale out technique.
For the experimental evaluation in [2], the authors used MySQL proxy software, Lua scripting language, application server, web server and database server. These are hosted on a virtual machine. The experiment was conducted using the Berkeley Cloud-stone benchmark. The experiment is to evaluate the behaviour of the SLA based provisioning of database against the traditional method of monitoring the utilization mechanism. The authors configured two read/write ratios 50/50 and 80/20.Workload starts with 50 users and increases by 20 users at some fixed time. There are 4 rules to achieve dynamic provisioning and elasticity for the database tier in

Get Access