Cloud Computing: Locally Sub-Clouds instead of Globally One Cloud

Cloud Computing: Locally Sub-Clouds instead of Globally One Cloud

Nawsher Khan (Universiti Malaysia Pahang, Malaysia), Noraziah Ahmad (Universiti Malaysia Pahang, Malaysia), Tutut Herawan (University Ahmad Dahlan, Indonesia) and Zakira Inayat (University of Engineering & Technology, Peshawar, Pakistan)
Copyright: © 2012 |Pages: 18
DOI: 10.4018/ijcac.2012070103
OnDemand PDF Download:
No Current Special Offers


Efficiency (in term of time consumption) and effectiveness in resources utilization are the desired quality attributes in cloud services provision. The main purpose of which is to execute jobs optimally, i.e., with minimum average waiting, turnaround and response time by using effective scheduling technique. Replication provides improved availability and scalability; decreases bandwidth use and increases fault tolerance. To speed up access, file can be replicated so a user can access a nearby replica. This paper proposes architecture to convert Globally One Cloud to Locally Many Clouds. By combining replication and scheduling, this architecture improves efficiency and easy accessibility. In the case of failure of one sub cloud or one cloud service, clients can start using another cloud under “failover” techniques. As a result, no one cloud service will go down.
Article Preview


Efficiency, scalability and easy accessibility are the key factors and should be the key features of cloud computing. From end-user computing, data storage and data transferring requirements are growing. Users demand for more capacity, more reliability and the capability to access information from anywhere in the world. Cloud services (computing, storage and transferring) meet this demand by providing transparent, easy and reliable solutions. Since late 2007 the concept of cloud computing was proposed (Weiss, 2007) and it has been utilized in many areas with some success (Brantner, Florescuy, Graf, Kossmann, & Kraska, 2008; Moretti, Bulosan, Thain, & Flynn, 2008). Cloud computing is deemed as the next generation of IT platforms that can deliver computing as a kind of utility (Buyya, Yeo, Venugopal, Broberg, & Brandic, 2009). Foster, Yong, Raicu, and Lu (2008) made a comprehensive comparison of grid computing and cloud computing.

By a cloud, we mean an infrastructure that provides resources and/or services over the Internet. A storage cloud provides storage services (block or file based services); a data cloud provides data management services (record-based, column-based or object-based services); and a compute cloud provides computational services. Often these are layered (compute services over data services over storage service) to create a stack of cloud services that serves as a computing platform for developing cloud-based applications. Examples include Google’s Google File System (GFS), BigTable and MapReduce infrastructure (Dean & Ghemawat, 2004; Ghemawat, Gobioff, & Leung, 2003). Amazon’s S3 storage cloud, SimpleDB data cloud, EC2 compute cloud (Amazon, 2009); and the open source Hadoop system (Borthakur, 2007; Dean & Ghemawat, 2008). Figure 1 shows the simple architecture of cloud computing.

Figure 1.

Simple architecture of cloud computing


For the majority of applications, databases are the preferred infrastructure for managing and archiving data sets, but as the size of the data set begins to grow larger than a few hundred terabytes, current databases become less competitive with more specialized solutions, such as the storage services (e.g., Borthakur, 2007; Dean & Ghemawat, 2008) that are parts of data clouds. For example, Google’s GFS manages Petabytes of data (Hbase Development Team, 2009).

Complete Article List

Search this Journal:
Open Access Articles: Forthcoming
Volume 12: 4 Issues (2022): Forthcoming, Available for Pre-Order
Volume 11: 4 Issues (2021): 3 Released, 1 Forthcoming
Volume 10: 4 Issues (2020)
Volume 9: 4 Issues (2019)
Volume 8: 4 Issues (2018)
Volume 7: 4 Issues (2017)
Volume 6: 4 Issues (2016)
Volume 5: 4 Issues (2015)
Volume 4: 4 Issues (2014)
Volume 3: 4 Issues (2013)
Volume 2: 4 Issues (2012)
Volume 1: 4 Issues (2011)
View Complete Journal Contents Listing