Abstract

Ensuring data correctness over partitioned distributed database systems is a classical problem. Classical solutions proposed to solve this problem are mainly adopting locking or blocking techniques. These techniques are not suitable for cloud environments as they produce terrible response times; due to the long latency and faultiness of wide area network connections among cloud datacenters. One way to improve performance is to restrict access of users-bases to specific datacenters and avoid data sharing between datacenters. However, conflicts might appear when data is replicated between datacenters; nevertheless change propagation timeliness is not guaranteed. Such problems created data uncertainty on cloud environments. Managing data uncertainty is one of the main obstacles for supporting global distributed transactions on the clouds. To overcome this problem, this paper proposes an quota-based approach for managing data uncertainty on the clouds that guarantees global data correctness without global locking or blocking. To decouple service developers from the hassles of managing data uncertainty, we propose to use a new platform service (i.e. Data Consistency as a Service (DCaaS)) to encapsulate the proposed approach. DCaaS service also ensures SaaS services cloud portability, as it works as a cloud adapter between SaaS service instances. Experiments show that proposed approach realized by the DCaaS service provides much better response time when compared with classical locking and blocking techniques.

Highlights

  • Clouds are the next-generation datacenters virtualized through hypervisor technologies, where cloud-vendors can dynamically provision their virtualized nodes on demand to their customers according to the specified service level agreements [3]

  • When a new DCaaS instance is added to the DCaaS peer network, the cloudlet quota of strong consistency objects specified in the Data Consistency Plan (DCP) has to be redistributed among all DCaaS service instances inside this cloudlet, and each DCaaS service instance should update its SCOQ list with the new quota values

  • This is done via a join DCaaS instance protocol, in which a new DCaaS service instance sends to the current cloudlet leader a join request

Read more

Summary

INTRODUCTION

Clouds are the next-generation datacenters virtualized through hypervisor technologies, where cloud-vendors can dynamically provision their virtualized nodes on demand to their customers according to the specified service level agreements [3]. Existing classical concurrency control and transaction management approaches (such as ones discussed in [7] [9]) are not suitable for cloud environments, as they opt to accommodate the slowest latency inside the cloud environment, which badly hurts services performance To overcome this problem, many approaches have appeared [4][5][6][8][20][22][24] proposing a restricted version of cloud computing, in which requests of users with similar latency values (known as a user-base) are directed to the closest datacenter such that no data sharing between datacenters is allowed. We argue that we need to create a new breed of database management services (such as transaction management, data access, and data replication) that take into consideration the data uncertainty resulting from the cloud non-homogenous timing model. This paper is the extended version of the paper proposed in [27]

AND RELATED WORK
SOLUTION MODEL AND ASSUMPTIONS
SERVICE DCP MANAGEMENT
DCP Definition and Creation
DCP Change Management
Objects Stabilization
DATA CONSISTENCY AS A SERVICE
DCaaS Structure and Configuration
DCaaS APIs
DCaaS Recovery
EXPERIMENTS
EXPERIMENTS RESULTS
VIII. CONCLUSION AND FUTURE WORK
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call