Date post: | 30-Dec-2015 |
Category: |
Documents |
Upload: | june-rogers |
View: | 219 times |
Download: | 0 times |
RACS: A Case for Cloud Storage Diversity
1
Hussam Abu-Libdeh,Lonnie PrincehouseHakim WeatherspoonCornell University
Problem
Vendor Lock-in:Longer time they use one cloud provider more data stored in this cloud provider harder and more expensive to transfer their data out (transfer in $$$$, transfer out $$$$) Lock in one cloud provider More vulnerable for price hikes/data center failures(Two main problems)
Stuck in one cloud provider
Outage and operation failure: physical failure Google Cloud unavailable Microsoft data center failure in Oct. 2009
Economic failures: budget now allowed Emerging new cheaper cloud Current cloud provider increase price
How to guard against Vendor Lock-in
First thought: Why not replicate their data into
multiple providers? ▪ Could not; three replicas, too expensive
Another way to create redundancy: ▪ Error Correcting code (such as RAID 5)
Design
Implemented as Proxy between client application and n- cloud storages Strip data into m
pieces, put them into m clouds, and generate (n-m) redundant data.
Conclusion
Identified an important problem: vendor lock-in
Proposed Redundant Array of Cloud Storage to solve this problem using erasure coding.
Tradeoff between overhead expense and vendor mobility
Simulations and experiments to prove the virtue for RACS.