On the Adoption of Erasure Code for Cloud Storage by Major Distributed Storage Systems

Aatish Chiniah,Avinash Mungur

doi:10.4108/eai.14-9-2021.170955

Abstract

INTRODUCTION: Traditional Cloud Systems are struggling to cope with the exponential growth of data in todays’ distributed application environment. The amount of data online has continuously increased since 2003. From an estimated 5 Exabyte in 2003 to 988 Exabyte in 2010. Presently it

Highlights

Traditional Cloud Systems are struggling to cope with the exponential growth of data in todays’ distributed application environment
This paper examines four Distributed File Systems (DFS), namely Sun’s Network File System (NFS), Andrew File System (AFS), Coda File System and Google File System (GFS)
The increasing amount of data and incapacity of traditional databases to handle those quantities of data has led to a new type of data store named as Distributed Storage Systems

Summary

Introduction

Traditional Cloud Systems are struggling to cope with the exponential growth of data in todays’ distributed application environment. It is estimated that 5 Exabyte of data are produced daily To cope with such astronomical load of data, Distributed Storage Systems such as Amazon, Google and Microsoft Azure are becoming the de-facto method for the storage of data. OBJECTIVES: The purpose of this paper is to assess the most used distributed storage systems using different evaluation criteria and identifying how erasure code can be integrated into them. CONCLUSION: This paper provides researchers in the field with a comprehensive review of Distributed Storage Systems and how the adoption of erasure codes will enhance their capabilities. The new generation of web applications requires the processing of terabytes or even petabytes of data. Such processing power can only be achieved by using distributed/parallel processing [2]. That is the underlying architecture which powers the world’s major web service providers such as Google, Amazon and Microsoft Azure

Objectives

Methods

Findings

Conclusion