Download the Full Version of textbook for Fast Typing at textbookfull.

com

Cloud Computing Principles Systems and

Applications 2nd Edition Nick Antonopoulos

https://textbookfull.com/product/cloud-computing-principles-
systems-and-applications-2nd-edition-nick-antonopoulos/

OR CLICK BUTTON

DOWNLOAD NOW

Download More textbook Instantly Today - Get Yours Now at textbookfull.com

 Recommended digital products (PDF, EPUB, MOBI) that
you can download immediately if you are interested.

Cloud Computing and Big Data: Technologies, Applications

and Security Mostapha Zbakh

https://textbookfull.com/product/cloud-computing-and-big-data-
technologies-applications-and-security-mostapha-zbakh/

textboxfull.com

Federal Cloud Computing The Definitive Guide for Cloud

Service Providers 2nd Edition Matthew Metheny

https://textbookfull.com/product/federal-cloud-computing-the-
definitive-guide-for-cloud-service-providers-2nd-edition-matthew-
metheny/
textboxfull.com

Project Management : Systems, Principles, and Applications

Badiru

https://textbookfull.com/product/project-management-systems-
principles-and-applications-badiru/

textboxfull.com

Virology Principles and Applications 2nd Edition Unknown

https://textbookfull.com/product/virology-principles-and-
applications-2nd-edition-unknown/

textboxfull.com
Cloud Computing CLOUD 2018 Min Luo

https://textbookfull.com/product/cloud-computing-cloud-2018-min-luo/

textboxfull.com

Energy Systems Modeling Principles and Applications Hooman

Farzaneh

https://textbookfull.com/product/energy-systems-modeling-principles-
and-applications-hooman-farzaneh/

textboxfull.com

Effective medium theory principles and applications 2nd

Edition Choy

https://textbookfull.com/product/effective-medium-theory-principles-
and-applications-2nd-edition-choy/

textboxfull.com

Assured cloud computing First Edition Campbell

https://textbookfull.com/product/assured-cloud-computing-first-
edition-campbell/

textboxfull.com

Mastering Bitcoin Unlocking Digital Cryptocurrencies 2nd

Edition Andreas M. Antonopoulos

https://textbookfull.com/product/mastering-bitcoin-unlocking-digital-
cryptocurrencies-2nd-edition-andreas-m-antonopoulos/

textboxfull.com
Computer Communications and Networks

Nick Antonopoulos
Lee Gillam Editors

Cloud
Computing
Principles, Systems and Applications
Second Edition
Computer Communications and Networks

Series editor
A.J. Sammes
Centre for Forensic Computing
Cranfield University, Shrivenham Campus
Swindon, UK
The Computer Communications and Networks series is a range of textbooks,
monographs and handbooks. It sets out to provide students, researchers, and non-
specialists alike with a sure grounding in current knowledge, together with com-
prehensible access to the latest developments in computer communications and
networking.
Emphasis is placed on clear and explanatory styles that support a tutorial
approach, so that even the most complex of topics is presented in a lucid and
intelligible manner.

More information about this series at http://www.springer.com/series/4198

Nick Antonopoulos • Lee Gillam
Editors

Cloud Computing
Principles, Systems and Applications

Second Edition

123
Editors
Nick Antonopoulos Lee Gillam
University of Derby University of Surrey
Derby, Derbyshire, UK Guildford, Surrey, UK

ISSN 1617-7975 ISSN 2197-8433 (electronic)

Computer Communications and Networks
ISBN 978-3-319-54644-5 ISBN 978-3-319-54645-2 (eBook)
DOI 10.1007/978-3-319-54645-2

Library of Congress Control Number: 2017942811

1st edition: © Springer-Verlag London Limited 2010

© Springer International Publishing AG 2017
This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of
the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation,
broadcasting, reproduction on microfilms or in any other physical way, and transmission or information
storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology
now known or hereafter developed.
The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication
does not imply, even in the absence of a specific statement, that such names are exempt from the relevant
protective laws and regulations and therefore free for general use.
The publisher, the authors and the editors are safe to assume that the advice and information in this book
are believed to be true and accurate at the date of publication. Neither the publisher nor the authors or
the editors give a warranty, express or implied, with respect to the material contained herein or for any
errors or omissions that may have been made. The publisher remains neutral with regard to jurisdictional
claims in published maps and institutional affiliations.

Printed on acid-free paper

This Springer imprint is published by Springer Nature

The registered company is Springer International Publishing AG
The registered company address is: Gewerbestrasse 11, 6330 Cham, Switzerland
Foreword

Since the first version of this book was published in 2010, with a foreword by my
colleague Mark Baker (University of Reading), considerable developments have
taken place in Cloud computing. Today, Cloud computing is no longer a niche
research area but now closely embedded in our everyday computing environment.
This is the ultimate success of a technology, which initially starts out as a specialist
domain-specific interest, but becomes so successful that it becomes invisible to us as
users. Systems such as Dropbox, Apple iCloud, Microsoft Office 365 and Google
Drive (amongst many others) are now regularly made use of and considered very
much a core fabric of our computing infrastructure. Social media platforms such
as Facebook, Twitter and Instagram all make use of Cloud systems and make use
of novel concepts such as “eventual consistency” (amongst others) as part of their
implementation. A mobile app that does not make use of a Cloud-based back end is
now an anomaly rather than a norm, a considerable change that has taken place since
2010. Early scientific Cloud systems, such as Eucalyptus, Open Cirrus, etc., once
considered the domain of computer science research, are now regularly used within
a variety of other communities, from biological sciences to arts and humanities.
Figure 1 shows change in interest (via Google trends) for the three terms “Cloud
computing” (dashed line, descending), “Internet of Things” (dashed line, slowly
ascending) and “big data” (dotted line) since the first edition of this book was
published in 2010. These three trends are closely related, as many applications
that generate or process large data sizes make use of Cloud-based infrastructure.
Similarly, many IoT devices act as data generators or consumers. It is also
interesting to see that programming models such as MapReduce, featured in the
2010 book, also appear in this version of the book but with a specific focus
on a dynamic Cloud computing environment. This programming model has now
been implemented across a variety of systems, from Hadoop (Cloudera, Apache)
to in-memory systems such as Apache Spark and Mesos (amongst others). This
programming model demonstrates how Cloud computing mechanisms have also
transformed data analysis and processing and has found wide-scale adoption in
industry and academia.

v
vi Foreword

Fig. 1 Google trends for Cloud computing, Internet of Things and big data

With significant commercial interest in Cloud computing due to its transfor-

mative impact on industry, the most prominent example of which is Amazon
Web Services (AWS), understanding how academic research could complement
rather than compete has been difficult. Whereas Cloud computing infrastructure
developers (Google Cloud, AWS, Microsoft Azure, Salesforce, etc.) often make
use of large-scale data centres with a large pool of servers, specialist energy
infrastructure and scalable/configurable networks, the academic community often
has limited access to such resources. Better understanding on how academic
researchers could respond to specialist challenges that may be commercially risky
for commercial vendors has changed since 2010. This book demonstrates many
such challenges that have been chosen by the academic community, such as (1)
Cloud federation, (2) adaptive and elastic resource allocation and (3) reproducibility
supported through Cloud-based systems. Whereas a particular industry vendor
would prefer a user to always make use of a single Cloud system, purchasing
and acquisition of computational infrastructure may not conform to this model,
often requiring a multi-system/Cloud environment. Understanding how commercial
Cloud systems could be “bridged” with private in-house systems, how a sudden
increase in workload could support “bursting” across multiple Cloud systems
and how services which are specialised for deployment over particular types of
infrastructure (such as GPUs) need to be integrated with services hosted on other
platforms (e.g. analytics or database services only available on a given platform)
remains an important challenge. Managing resources and efficient allocation within
such a federation remain important academic research challenges, which often
complement work being carried out in industry.
Foreword vii

The significant growth and capability of edge devices, and how these can be
combined with Cloud-based data centres, has also seen considerable interest over
recent years. In 2010, edge devices generally comprising of sensors were primarily
used as mechanism for data capture. With increasing advances in semiconductor
technologies, edge devices today have significant processing capability (e.g. the use
of Arduino, Raspberry Pi 3, Intel Edison, etc.) enabling data to be preprocessed and
sampled at the network edge, prior to being transmitted to a centralised data centre.
Another significant trend since 2010 has been the wider adoption and availability of
programmable networks through software-defined networks and network function
virtualisation technologies. The availability of a more complex capability at the
network edge, along with in-network programmability, changes the role of a data
centre. This perspective requires researchers to better understand how edge devices
and data centres can be used collectively. Understanding what should be done
at the network edge vs. in the data centre becomes an important consideration.
In 2010, a key requirement was to understand how processing and data could
be “offloaded” from a mobile/edge device to a Cloud data centre (to conserve
battery power of the edge device and avoid the impact of intermittent network
connectivity). Today the focus has shifted to “reverse offloading”, i.e. understanding
how processing to be carried out within a Cloud data centre could be shifted to
edge devices – to limit large data transfer over a public network and avoid latency
due to such transfers. Better and more effective use of edge devices (alongside
the use of a data centre) also leads to useful ways of supporting data security
(i.e. a user can decide what should remain on the devices vs. what to shift to the
data centre). The programming models needed to support this collaborative and
opportunistic use of edge devices and data centres remain in short supply at present.
Recent availability of low-overhead (in terms of memory/storage requirements and
scheduling delay) “container” technologies (such as Docker, Kubernetes, Red Hat
OpenShift) also provides useful mechanisms for supporting edge device/Cloud data
centre integration, enabling services to be migrated (offloaded) from edge devices
to data centres (and vice versa) – Villari et al.1 refer to this as “osmotic computing”.
Virtualisation technologies have also seen a considerable improvement since
2010. The capability to virtualise various parts of our computing infrastructure
(from processors, networks, edge devices, storage, etc.) and services (such as a
firewall) has seen considerable growth. The “virtualised enterprise” vision now
dominates thinking in many resource management systems, aiming to make more
effective use of resources across different applications. Understanding how the
memory requirements and switching overhead of virtual machines (VMs) could be

1
M. Villari, M. Fazio, S. Dustdar, O. Rana and R. Ranjan, “Osmotic Computing: A New Paradigm
for Edge/Cloud Integration”, IEEE Cloud Computing, December 2016. IEEE Computer Society
Press.
viii Foreword

reduced has led to interest in container technologies. Some predict that the days
of VM-based deployments are limited, due to benefits observed with containers.
How such approaches can be made multiplatform and support federation remain
important challenges in this context.
The editors of this book have selected an excellent combination of chapters that
cover these emerging themes in Cloud computing – from autonomic resource man-
agement, energy efficiency within such systems and new application requirements
of such technologies. The book will provide valuable reference material for both
academic researchers and those in industry to better gauge current state of the art in
Cloud-based systems.

Professor of Performance Engineering Omer F. Rana

Cardiff University, Cardiff, UK
Preface

1. Introduction

The first edition of this book, back in 2010, started by identifying the relatively
recent emergence of Cloud and the increasing demand for Cloud systems and
services that was apparent. We suggested, back then, that its meaning was hotly
debated and identified specific IT and e-commerce vendors – Amazon, Google,
IBM, Microsoft and Sun – who seemed to be leading the charge in making pay-per-
use access to a wide variety of third-party applications and computational resources
on a massive scale available widely. We also identified how the notion of Clouds
seems to blur the distinctions between grid services, web services and data centres.
In the time that has elapsed between the first edition and this second edition,
it would be fair to say that Cloud has not only emerged but has become a go-
to for both experimental and developmental uses and is variously at the core of
numerous businesses across the globe. For some, the use of Cloud in many of
their activities is either second nature or is otherwise unavoidable. The definitional
debates at a broad level have subsided, with a purportedly final perspective – at the
16th version – offered by the US National Institute of Standards and Technology
(The NIST Definition of Cloud Computing, NIST Special Publication 800–145).2
This is completed by the subsequent production in 2014 of ISO/IEC 17788, Cloud
computing – Overview and vocabulary, although these two are not perfectly aligned,
as well as ISO/IEC 17789, Cloud computing – Reference architecture. Of the
five vendors we had acknowledged before, four remain and would probably now
be considered the biggest Cloud players at this point in time, not least because
their reported Cloud revenues are now in the billions of dollars per quarter: Sun’s
Network.com which had originally appeared to be a well-timed foray is, for most
and perhaps unfortunately, a slightly distant memory following Sun’s acquisition by

2
http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf – doi:10.6028/
NIST.SP.800–145.

ix
x Preface

Oracle, with the memory of Sun as a company becoming equally distant. And for
these big four, not only is the scale of their Cloud operations substantial, as it needs
to be, but the range of services now available is also substantial and growing. And in
terms of blurred distinctions, Cloud variously supports or subsumes these – running
in, and across, multiple data centres in a large number of geographical jurisdictions
and supporting grid, web and mobile services amongst others.
As the subject has grown, so topic coverage has extended. Many new Cloud-
based services are a commoditisation of decreasingly common computational needs,
albeit with a few with broad application. Given the inherent economies of scale
brought to such commoditisation, this is likely to put further pressure on companies
that are (still) trying to compete in Cloud. And, indeed, this has already led to
some companies who have tried to compete withdrawing their attempts to keep
pace and in one particular large company case closing down their public Cloud
entirely. Various reasons may be cited: one key reason will be the sheer scale of
investment needed to address the inherently high costs of building and running
large new data centres and of continuing to ensure these comprise the latest and
most capable hardware within a highly competitive pricing environment. The result,
of not being able to compete at this level, tends to be that the arena for competition
shifts up the stack, with consultancies and commentators of various hues espousing
the benefits to be gained using multiple, and potentially federated, Clouds (multi-
Cloud). This also adds opportunities in Cloud brokerage, in adding value or getting
the best performance per unit of cost, and also in Cloud orchestration, with the need
to simplify the complexities of using a multiplicity of services simultaneously. And
the continued focus on Cloud security shows no sign of abating at any time soon.
Cloud is also, arguably, the springboard for the emergence of various other
significant topics of interest. The scale of storage and computational capability
available supports the treatment of big data, not only of large static collections but
also of the kinds of streaming sensor data important in the Internet of Things and the
combination of big and streaming data. In turn, Cloud acts as an enabler for activities
in so-called smart cities and in supporting operation of connected and autonomous
vehicles. And although software, platform and infrastructure remain the mainstay of
service models, these also now address containers (e.g. with Docker in Amazon’s
Elastic Container Service, Microsoft Container Service, Google Container Engine
and IBM Containers) and microservices (AWS Lambda, Microsoft Azure Functions,
Google Cloud Functions and IBM OpenWhisk); the latter abstracts away from the
lower levels of the stack, as well as offering pricing based on compute time used
as multiples of milliseconds rather than hours. With the relative maturity of such
offerings, as well as the emergent next generations of mobile telecommunications
related to network function virtualisation and mobile edge Cloud computing,
increased focus on distributed computation and computational offloading may also
be anticipated.
Given the extent described above, any collection such as this can only ever offer
insights into select subsets of what exists – as, indeed, have the paragraphs above.
Research around these areas abounds and will continue to grow, with the growth
Preface xi

in number and diversity of Cloud conferences and workshops and special issues
of very many journals that are variously Cloud flavoured, as a crude but effective
measure of reach, coverage and scope. However, the four cornerstones of quality of
service, embodied in the first edition, remain consistent:
1. Efficiency: The need for execution and coordination of the services to be
optimised in terms of data traffic and latency remains, even with lower-latency
communications, in part due to growth of data and ability to process it. Data
traffic is typically one of the main cost factors in any distributed computing
framework, and thus its reduction is a standard long-term goal of such systems.
Latency is arguably one of the most important factors affecting customer
satisfaction, and therefore it should also be within specified acceptable limits.
And efficiencies in performance per unit cost are of particular importance.
2. Scalability: Cloud service offerings of various kinds continue to need to scale
well to support massive customer bases. They must continue to withstand
demand of a great many bursty applications during peak times and endure the
“flash crowd” phenomenon familiar in overly successful marketing strategies and
provisioning for popular websites at key times. There is evidence to suggest, also,
that great scale can dissipate distributed denial of service attacks, albeit at a price.
However, applications must also be architected to be able to operate at scale.
3. Robustness: Cloud services still need continuously high availability by design,
with effective use of redundancy and graceful failover. With users charged for
the expected successful use of computational facilities, it remains imperative
to understand and address the risk of failure, either to help to mitigate the
probability of failure or to use this information to offer appropriate compensation
schemes. Some high-profile Cloud users are known to make deliberate efforts to
disrupt their own systems in order to prove to themselves that any impact on the
services is minimised, which again relates to appropriate architecting.
4. Security: Appropriate security provisions are now, quite simply, a fundamental
expectation for both data and applications to protect both the providers and
consumers from malicious or fraudulent activities and must recognise the
responsibilities of each with respect to the other.
In respect to various Cloud topics, this edition carries the following key
objectives:
1. To present and explore the principles, techniques, protocols and algorithms that
are used to design, develop and manage Clouds
2. To present current Cloud applications and highlight the use of Cloud technologies
to manage data and scientific analysis
3. To present methods for linking Clouds and optimising their performance
All three objectives are firmly rooted in extant discourse of distributed computing
and a desire to understand the potential of all these technologies in constructing
purpose-specific Cloud solutions that successfully address commercial demand and
shape successful business.
xii Preface

2. Expected Audience

This book should be of particular interest for the following audiences:

• Researchers and doctoral students working on certain aspects of Cloud com-
puting research, implementation and deployment, primarily as a reference
publication. Similarly, this book should be useful to researchers in related or
more general fields, such as distributed computing, software engineering, web
services, modelling of business processes and so on.
• Academics and students engaging in research-informed teaching in the above
fields. This book can serve as a good collection of articles to facilitate a good
understanding of this subject and as such may be useful as a key reference text in
such teaching.
• Professional system architects and developers who could decide to adapt and
apply in practice a number of techniques and processes presented in the book.
• Technical managers and IT consultants who would consider this as a book that
demonstrates the potential applicability of certain methods for delivering efficient
and secure commercial services to customers globally.
These audiences will find this publication appealing as it combines three distinct
scholarly contributions: firstly, it identifies and highlights current techniques and
methods for designing Cloud systems and optimising their performance; secondly,
it presents mechanisms and schemes for developing Clouds to manage data and
produce scientific analysis and economic activities; and thirdly, it provides a
coverage of approaches and technologies used to link Clouds together and manage
heterogeneity.

3. Book Overview

The book contains 14 chapters that were carefully selected based on peer review
by at least two expert and independent reviewers. The chapters are split into five
parts:

Part I: General Principles

This part aims to cover the essential technical characteristics and concepts behind
the new developments in Cloud computing. The chapters included in this part
collectively introduce the reader to essential architectural principles behind the
new developments and how these advances are influencing the applications, how
Preface xiii

to measure the performance of new Cloud architectures and how to do effective

resource management in the emerging Clouds for improved quality of service and
performance.
Chapter 1 provides a taxonomy and survey to highlight the rapid technological
advancements in Cloud computing and how it will transform silos into to the so-
called Internet of Things (IoT). This chapter discusses the principles and taxonomy
behind emerging trends in Cloud computing such as edge computing (Cloudlets and
fog computing), IoT (smart grids, smart cities) and big data.
Chapter 2 describes the resource estimation problem that, if not addressed, will
either overestimate or underestimate the resources, leading to wasted resources or
poor performance. This chapter addresses the problem of dimensioning the amount
of virtual machines (VMs) in Clouds and presents approaches that estimate in a
static or dynamic way the amount of VMs for several types of applications.
Chapter 3 reviews the important approaches for resource monitoring in virtual
machines. Taxonomy is presented that, when applied to different solutions that
use or augment virtual machines, can help in determining their similarities and
differences. The process of classification and comparing systems is detailed, and
several representative state-of-the-art systems are evaluated.

Part II: Science Cloud

This part builds on the principles and approaches of Part I and provides an in-
depth coverage of how Clouds can be designed to produce scientific insights and
analysis. This part describes important aspects of scientific applications such as
agility, reproducibility, consistency and scalability. It includes chapters that propose
novel techniques and systems for making Clouds reproducible, agile and consistent.
Chapter 4 introduces elasticity, which helps in determining the most appropriate
set of resources for running scientific applications whose requirements cannot be
determined in advance. It describes elasticity taxonomy and how this can be used
in running scientific applications. A discussion about good practices as well as an
analysis of the state of the art is described.
Chapter 5 characterises terms and requirements related to scientific repro-
ducibility. Clouds can play a key role by offering the infrastructure for long-term
preservation of programmes and data. This chapter describes how Clouds can aid
the development and selection of reproducibility approaches in science.
Chapter 6 describes the challenges in integrating clinical and genomic data
and producing insights from it. Integration complexity, data inconsistency and
scalability of the underlying data infrastructures have been highlighted as the main
challenges. Cloud approaches to storing huge amounts of clinical and genomic data
and producing value from it are also described.
xiv Preface

Part III: Data Cloud

This part provides an overview of novel approaches in producing scalable, high-

performance and decentralised Cloud systems. This provides an overview of how
emerging technologies such as P2P and graph systems fit with Cloud computing to
enable fault-tolerant, scalable and high-performance data-intensive Clouds.
Chapter 7 describes the challenges of implementing graph-based systems and
frameworks. The focus is on the problem of creating scalable systems for storing
and processing large-scale graph data on HPC Clouds. It highlights a graph
database benchmarking framework and its use in analysing the performance of
graph database servers.
Chapter 8 describes a framework that exploits a peer-to-peer (P2P) model to
manage systems failures of MapReduce and their recovery in a decentralised but
effective way. It describes the architecture and performance results of the proposed
model, which shows a higher level of fault tolerance compared to a centralised
implementation of MapReduce.

Part IV: Multi-clouds

This part presents ideas on achieving federation and interoperability across Clouds
and using autonomic computing and other intelligent approaches to self-manage the
federated Clouds. It includes chapters that propose novel techniques and systems
for making Cloud data and application interoperable as well as achieving data and
compute interoperability through automated means.
Chapter 9 presents an architecture to facilitate federated Clouds for achieving
interoperability between Clouds, especially application and data-level interoperabil-
ity. It describes the design of the architecture, implementation choices and some
practical evaluations for monitoring multiple Cloud deployments to make informed
decisions.
Chapter 10 provides an overview of the concepts that are being used in practice
and theory in order to advance the field of self-managing and self-healing Clouds.
It describes approaches to providing self-managed data- and compute-intensive
services to the users by overcoming heterogeneity in terms of computing resources.

Part V: Performance and Efficiency

This part covers a range of challenging issues associated to Cloud data centres
that, if not addressed properly, may limit its adoption. It includes chapters on
Preface xv

Cloud operations and Cloud economy offering approaches that can bring down
Cloud operation costs. It also includes chapters on resource management approaches
leading to energy efficiency and predictive workload management.
Chapter 11 presents a Cloud brokering model, which can reduce Cloud cus-
tomers’ costs when compared to traditional on-demand renting costs. It proposes
a number of online and offline heuristics to efficiently manage the resources of
the broker in order to optimise its revenue, as well as the QoS level offered to the
customers.
Chapter 12 proposes a resource management model with the aim of improv-
ing energy efficiency and reliability. The model manages the problem of over-
provisioning of resources and to an underutilisation of the active servers. Using
an evolutionary optimisation algorithm, the model can efficiently map user requests
with the available hardware resources.
Chapter 13 describes an approach to manage Cloud data centres by observing
workload behaviours and server usage patterns in the past. The analysis presented
in this chapter can support Cloud providers for achieving efficient data centre
management and prediction analytics in Cloud data centres.
Chapter 14 presents energy-efficient browsing approach that ranks URL and
web domains based on web page-induced energy consumption. The approach can
achieve substantial resource reduction for CPU and memory usage. It is also able to
reduce bandwidth usage without any degradation to user experience.
Acknowledgements

The editors are grateful to the peer review panel for supporting this book including
Miyuru Dayarathna, Daniel de Oliveira, Vincent C. Emeakaroha, Teodor-Florin
Fortiş, Imen Ben Fradj, Luiz Manoel Rocha Gadelha Júnior, Guilherme Galante,
Santiago Iturriaga, Sara Kadry, Somnath Mazumdar, Bhaskar Prasad Rimal, José
Simão and Domenico Talia.
The editors are also grateful to their respective families for continuing to afford
them the time to produce works such as this.
The editors wish to thank Springer’s team for their strong and continuous support
throughout the development of this book.
The editors are also deeply apologetic to anyone that they may have forgotten.

Derby, UK Nick Antonopoulos

Guildford, UK Lee Gillam
Winter 2016

xvii
Contents

Part I General Principles

1 The Rise of Cloud Computing in the Era of Emerging
Networked Society . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Bhaskar Prasad Rimal and Ian Lumb
2 Mirror Mirror on the Wall, How Do I Dimension My Cloud
After All? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Rafaelli Coutinho, Yuri Frota, Kary Ocaña, Daniel de Oliveira,
and Lúcia M.A. Drummond
3 A Taxonomy of Adaptive Resource Management Mechanisms
in Virtual Machines: Recent Progress and Challenges . . . . . . . . . . . . . . . . . 59
José Simão and Luís Veiga

Part II Science Cloud

4 Exploring Cloud Elasticity in Scientific Applications . . . . . . . . . . . . . . . . . . 101
Guilherme Galante and Rodrigo da Rosa Righi
5 Clouds and Reproducibility: A Way to Go to Scientific
Experiments?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Ary H. M. de Oliveira, Daniel de Oliveira, and Marta Mattoso
6 Big Data Analytics in Healthcare: A Cloud-Based Framework
for Generating Insights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Ashiq Anjum, Sanna Aizad, Bilal Arshad, Moeez Subhani,
Dominic Davies-Tagg, Tariq Abdullah, and Nikolaos Antonopoulos

Part III Data Cloud

7 High-Performance Graph Data Management and Mining
in Cloud Environments with X10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Miyuru Dayarathna and Toyotaro Suzumura

xix
xx Contents

8 Implementing MapReduce Applications in Dynamic Cloud

Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Fabrizio Marozzo, Domenico Talia, and Paolo Trunfio

Part IV Multi-clouds
9 Facilitating Cloud Federation Management via Data
Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Vincent C. Emeakaroha, Phillip Healy, and John P. Morrison
10 Applying Self-* Principles in Heterogeneous Cloud Environments . . . 255
Ioan Drăgan, Teodor-Florin Fortiş, Gabriel Iuhasz, Marian Neagul,
and Dana Petcu

Part V Performance and Efficiency

11 Optimizing the Profit and QoS of Virtual Brokers in the Cloud . . . . . . 277
Santiago Iturriaga, Sergio Nesmachnow, and Bernabé Dorronsoro
12 Adaptive Resource Allocation for Load Balancing in Cloud . . . . . . . . . . 301
Somnath Mazumdar, Alberto Scionti, and Anoop S. Kumar
13 Datacentre Event Analysis for Knowledge Discovery
in Large-Scale Cloud Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
John Panneerselvam, Lu Liu, and Yao Lu
14 Cloud-Supported Certification for Energy-Efficient Web
Browsing and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Gonçalo Avelar, José Simão, and Luís Veiga

Author Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Subject Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

 Part I
General Principles
Chapter 1
The Rise of Cloud Computing in the Era
of Emerging Networked Society

Bhaskar Prasad Rimal and Ian Lumb

1.1 Introduction

In 2009, Rimal et al. [1] published a very first taxonomy and survey that defined the
field, described many issues and opportunities, and summarized the developments of
cloud computing up to that point. We refer readers to our original paper [1] to better
understand the fundamentals of cloud computing and the descriptions of potential
applications. Since then, the role and scope of cloud computing has remarkably
changed. In this chapter, our aim is a complement to that taxonomy and survey,
denoting the rapid technological advancements since then. Cloud computing has
been widely deployed and become a major backbone of every other technology –
from cellular phones through to wearables, connected vehicles, and the future
networked society. The networked society is the networks of everything (NoE), that
is, beyond the upcoming 5G networks.
Our vision of networked society is not only about wired/wireless communica-
tions but creating an ecosystem of device vendors, application developers, network
operators, telecom operators, and cloud services/infrastructure providers to create
a foreseeable new business value chain that will not only accelerate every area
but also bring new innovative ideas and services. Those services are accessible
to anyone (e.g., devices, human, robots, automobiles) to connect each other and
share data from anywhere and anytime. However, there is still no well-defined
standard definition and requirements of the networked society. Therefore, there is

B.P. Rimal ()

University of Québec, INRS, Montŕeal, QC, Canada
e-mail: [email protected]
I. Lumb
York University, Toronto, ON, Canada
Univa Corporation, Hoffman Estates, IL, USA

© Springer International Publishing AG 2017 3

N. Antonopoulos, L. Gillam (eds.), Cloud Computing, Computer Communications
and Networks, DOI 10.1007/978-3-319-54645-2_1
4 B.P. Rimal and I. Lumb

a need for a taxonomy of enabling technologies of networked society to better

understand the concept and advance the state of the art. This chapter provides a
holistic understanding of networked society.
Furthermore, given the wide variety of communications (e.g., machine-to-
machine communications, human-to-machine communication, human-to-robot
communications) and applications in the networked society, a single communication
technology is likely not able to meet such heterogeneity. We may need a
convergence or integration of different wired/wireless communication technologies
to truly address the complexity of the networked society. Cloud computing
technologies are the major backbone for networked society, where billions of
devices will be connected anytime to each other and access a wide variety of
services anywhere. Toward this end, the focus and contributions of this chapter are
as follows:
• First, we revisit the scope and role of cloud computing and extend them in the
context of networked society, paying particular attention to scope and emerging
areas of cloud computing.
• Second, we propose a taxonomy of enabling technologies of networked society.
This will be an instrument to understand the vision, the overall concept, and
the enabling technologies of networked society. To the best of the authors’
knowledge, this is a first taxonomy of enabling technologies of the networked
society.
• Third, we describe each enabling technology of networked society based on the
proposed taxonomy and pay close attention to some of the particular challenges
and opportunities that may be used by other researchers as a baseline for future
research in the area of networked society.
The remainder of the chapter is structured as follows. Section 1.2 provides an
overview of cloud computing in a nutshell, including cloud service modes and
deployment modes. Section 1.3 introduces a networked society and presents a
proposed taxonomy of enabling technologies of networked society. Further, each
enabling technology is discussed, including issues and opportunities in great detail.
Finally, Sect. 1.4 concludes the chapter.

1.2 Cloud Computing in Nutshell

Cloud computing implements the idea of utility computing, which was first coined
by Professor John McCarthy in 1961, where computing was viewed as a public
utility just as the telephone system. Later, this idea resurfaced in new forms as
cloud computing. There is a plethora of definitions for cloud computing, from both
academia and industry. Among them, Rimal et al. [2] defined cloud computing as,
a model of service delivery and access where dynamically scalable and virtualized
resources are provided as a service over the Internet. Cloud computing provides
a paradigm shift of business and IT, where computing power, data storage, and
1 The Rise of Cloud Computing in the Era of Emerging Networked Society 5

services are outsourced to third parties and made available as commodities to

enterprises and customers. Cloud computing is a center point for the most highly
impactful technologies such as mobile Internet, automation of knowledge work, the
Internet of Things (IoT), and big data. Further, cloud offers tremendous economic
benefits. For example, the total economic impact of cloud technology could be $1.7–
$6.2 trillion annually in 2025, and the proliferation and sophistication of cloud
services could become a major driving force in making entrepreneurship more
feasible in the coming decade [3]. However, there are several challenges to be
addressed. The taxonomy, survey, challenges, and opportunities of cloud computing
are thoroughly studied in [4].

1.2.1 Service Models and Deployment Modes of Cloud

Computing

Cloud service models can be classified into three groups: Software-as-a-Service

(SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS). The
deployment modes can be categorized into three groups: public cloud, private cloud,
and hybrid cloud. We discuss them briefly in the following subsections.

1.2.1.1 Cloud Service Models

(1) Software-as-a-Service (SaaS): SaaS, commonly referred to as the Application

Service Provider model, is heralded by many as the new wave in application
software delivery. Further, SaaS can be view as a multi-tenant cloud platform [5].
It shares common resources and a single instance of both the object code of an
application as well as the underlying database to support multiple customers simul-
taneously. Key examples of SaaS provider include SalesForce.com,1 NetSuite,2
Oracle,3 IBM,4 and Microsoft (e.g., Microsoft Office 3655 ).
(2) Platform-as-a-Service (PaaS): It is the big idea to provide developers with
a platform including all the systems and environments comprising the end-to-
end life cycle of developing, testing, deploying, and hosting of sophisticated web
applications as a service delivered by a cloud. It provides an easier way to develop
business applications and various services over the Internet. Key examples of

1
SalesForce: https://www.salesforce.com/, Accessed Nov. 2016.
2
NetSuite: http://www.netsuite.com/, Accessed Nov. 2016.
3
Oracle: https://www.oracle.com/cloud/saas.html, Accessed Nov. 2016.
4
IBM: https://www.ibm.com/cloud-computing/solutions/, Accessed Nov. 2016.
5
Microsoft Office 365: https://products.office.com/en-us/office-online/documents-spreadsheets-
presentations-office-online, Accessed Nov. 2016.
6 B.P. Rimal and I. Lumb

PaaS are Google AppEngine6 and Microsoft Azure,7 just to name two. PaaS can
slash development time and offer hundreds of readily available tools and services
compared to conventional application development.
(3) Infrastructure-as-a-Service (IaaS): IaaS is the delivery of resources (e.g.,
processing, storage, networks) as a service over Internet. Aside from the higher
flexibility, a key benefit of IaaS is the usage-based payment scheme. This allows
customers to pay as you grow. Key examples are Amazon EC2,8 GoGrid,9 Flexis-
cale,10 Layered Technologies,11 AppNexus,12 Joyent,13 and Mosso/Rackspace.14

1.2.1.2 Cloud Deployment Modes

(1) Public Cloud: It describes the cloud computing in the traditional mainstream
sense, whereby resources are dynamically provisioned on a fine-grained, self-
service basis over the Internet, via web applications/web services, from an off-site
third-party provider who shares resources. Some examples are Zimory,15 Microsoft
Azure, Amazon EC2, GigaSpaces,16 Rackspace, and Flexiscale.17
(2) Private Cloud: Data and processes are managed within the organization
without the restrictions of network bandwidth, security exposures, and legal require-
ments that using public cloud services across open, public networks might entail.
Some examples are Amazon VPC,18 Eucalyptus,19 OpenStack,20 VMWare,21 and
Intalio.22

6
Google AppEngine: https://console.cloud.google.com/projectselector/appengine, Accessed Nov.
2016.
7
Microsoft Azure: https://azure.microsoft.com/en-us/?b=16.26, Accessed Nov. 2016.
8
Amazon EC2: https://aws.amazon.com/ec2/, Accessed Nov. 2016.
9
GoGrid: https://www.datapipe.com/gogrid/, Accessed Nov. 2016.
10
Flexiscale: http://www.flexiscale.com/, Accessed Nov. 2016.
11
Layered Technologies: https://www.datapipe.com/layered_tech/, Accessed Nov. 2016.
12
AppNexus: https://www.appnexus.com/en/platform, Accessed Nov. 2016.
13
Joyent: https://www.joyent.com/, Accessed Nov. 2016.
14
Mosso/Rackspace: https://www.rackspace.com/cloud, Accessed Nov. 2016.
15
Zimory: http://www.zimory.com/, Accessed Nov. 2016.
16
GigaSpaces: http://www.gigaspaces.com/HP, Accessed Nov. 2016.
17
Flexiscale: http://www.flexiscale.com/, Accessed Nov. 2016.
18
Amazon VPC: https://aws.amazon.com/vpc/, Accessed Nov. 2016.
19
Eucalyptus: http://www8.hp.com/us/en/cloud/helion-eucalyptus.html, Accessed Nov. 2016.
20
OpenStack: https://www.openstack.org/, Accessed Nov. 2016.
21
VMWare: https://www.vmware.com/, Accessed Nov. 2016.
22
Intalio: http://www.intalio.com/, Accessed Nov. 2016.
1 The Rise of Cloud Computing in the Era of Emerging Networked Society 7

(3) Hybrid Cloud: The environment is consisting of multiple internal and/or exter-
nal providers. Some examples are RightScale,23 Asigra Hybrid Cloud Backup,24
QTS,25 and Skytap.26

1.3 Networked Society

A conventional definition of networked society states that a number of major social,

technological, economic, and cultural transformations came together to give rise
to a new form of society, the so-called networked society. A focal point of the
networked society is the transformation of the realm of communications [6, 7]. In a
broader perspective of information, communications and technologies (ICTs), and
beyond 5G networks (refer Sect. 1.3.1), networked society can be defined as a new
paradigm and is not only about technology, but it creates an ecosystem of device
vendors, application developers, network operators, telecom operators, and cloud
services/infrastructure providers to create a foreseeable new business value chain
that will not only accelerate every area but also brings new innovative ideas and
services. Cloud technologies became a major part of networked society.
Figure 1.1 presents a hypothetical scenario that is suggestive of the near future
we hope to create by leveraging the benefits of cloud computing in the networked
society. The networked society is beyond future 5G networks. It is more than more
data and massive end-to-end connectivity of the things. Networked society is not just
incremental research but game changers for the quality and experience of people’s
life that will be more intelligent, more immersive experience enriched by context-
aware services (e.g., mixed augmented and virtual reality) and automated, secure,
sustainable, green, and more knowledgeable society. Furthermore, that will also
create a new scientific concept toward industrial and social innovations.

Jony is 65 years old and medically paralyzed man. One day Jony feels sick and asks personal
assistant robot to call the hospital. The personal assistant robot then calls the hospital emer-
gency number and requests further assistance. The hospital authority then sends self-driving
car to Jony’s home. The personal assistant robot puts Jony into the self-driving car. Then the
self-driving car takes him to the hospital. On the way to hospital doctors were monitoring
Jony’s health status remotely. At the hospital, a specialist doctor performs remote surgery
with actuating robots to save his life.

Fig. 1.1 Hypothetical scenario of the next generation of cloud computing: connecting everything
from everywhere via cloud in the networked society

23
http://www.rightscale.com/, Accessed Nov. 2016.
24
Asigra: http://www.asigra.com/cloud-backup-software, Accessed Nov. 2016.
25
http://www.qtsdatacenters.com/, Accessed Nov. 2016.
26
https://www.skytap.com/, Accessed Nov. 2016.
8 B.P. Rimal and I. Lumb

Cloud Computing

Internet of Things (IoT)

(Smart Grids, Smart Cities)
Edge Computing
(Cloudlet, MEC,
Fog Coputing)
Big Data

Augmented,Virtual,
Enabling Technologies and Mixed Reality
Containerization
for
Networked Society
Tactile Internet
Network Slicing

Network Function
Software-Defined
Virtualization (NFV)
Networking (SDN) 4G LTE/LTE-Advanced,
5G networks

Fig. 1.2 Proposed taxonomy of enabling technologies of the networked society

1.3.1 Taxonomy of Enabling Technologies of

Networked Society

Pervasiveness and emerging technological trend of cloud computing disrupts indus-

tries across the world, and companies look forward to maximize and implement
cloud as a strategic and integral technology to create value chain and business
agility. This will create a huge opportunity in the networked society era of disruptive
innovation. The proposed taxonomy of enabling technologies of networked society
is shown in Fig. 1.2. In the next section, we provide a more detailed description of
each enabling technology.

1.3.1.1 Edge Computing: Cloudlet, Fog Computing,

and Mobile-Edge Computing

Cloudlet: A cloudlet (also known as edge cloud) is a powerful computer or

computer cluster that can be viewed as a data center in a box whose goal is to
bring the cloud one wireless hop away from the mobile devices, thereby maintaining
logical proximity (low latency, high bandwidth). Further, it can be viewed as a new
architectural element that represents the middle tier of a three-tier hierarchy: mobile
device, cloudlet, and cloud [8]. The cloudlet host runs a hypervisor (e.g., KVM) in
order to host multiple virtual machines (VMs). Those VMs publish information
(e.g., OS and other properties) to the network. The cloudlet client (e.g., smart
phones, PDAs, wearable devices) discovers the cloudlet server through information
(cloudlet server IP address and port) broadcasted by the discovery service residing
1 The Rise of Cloud Computing in the Era of Emerging Networked Society 9

in a cloudlet host. The client then establishes an HTTP connection to the cloudlet
server for VM overlay27 transmission and uploads the overlay [8–10]. The cloudlet
decompresses this overlay and applies it to the baseVM to derive the launchVM and
then creates a VM instance from it. Afterward, the mobile client starts offloading
operation on that instance. The mobile device uses Wi-Fi or cellular data service of
4G LTE depending on the deployment scenarios of cloudlet to reach Internet and
then remote cloud (e.g., Amazon EC2).
Cloudlet supports resource-intensive and interactive mobile applications by
providing computing resources to mobile devices with low latency. Key features of
cloudlets include near-real-time, just-in-time provisioning of applications to edge
nodes and handoff of virtual machines seamlessly from one node to another once a
user has moved away from its first node.
Potential application areas of cloudlet are enormous. More specifically, the appli-
cations (e.g., video streaming, speech processing, cognitive assistance applications,
augmented and virtual reality, edge analytics in IoT, new automotive services, drone,
just to name a few) which have stringent QoS requirements, such as low latency and
real time, can all benefit from cloudlets.
Fog Computing: Cisco envisioned the concept of Fog computing in 2012. Fog
computing is a highly virtualized platform, which extends the cloud computing
to the edge of networks, thereby enabling applications and services on billions of
connected devices, especially, in the Internet of Things (IoT) [11]. Example includes
Cisco IOx that combines IoT application execution within the fog computing and
offers highly secure connectivity with Cisco IOS technology. Some of the major
characteristics of Fog computing are listed below:
• Fog nodes (i.e., provide compute, storage, and network capabilities) are typically
located away from the main cloud data centers.
• Fog nodes provide applications with awareness of device geographical location
and device context.
• Fog nodes offer special services that may only be required in the IoT context
(e.g., translation between IP and non-IP transport).
• Support for online analytics and interplay with the cloud
Fog computing may have a wide range of applications such as connected vehicle,
smart grid, smart cities, pipeline monitoring, connected rail, smart traffic light sys-
tems, machine-to-machine (M2M) communications, or human-machine interaction
(HMI), just to name a few.
Mobile-Edge Computing: The European Telecommunications Standards Institute
(ETSI) launched an industry specification for mobile-edge computing (MEC) in
September 2014. The ETSI defined MEC as: Mobile-edge Computing transforms

27
The compressed binary difference between the baseVM (i.e., a VM with a minimally configured
guest operating system installed) image and the launchVM (i.e., VM image used for offloading)
image is known a VM overlay [8, 9].
10 B.P. Rimal and I. Lumb

base stations (e.g., 2G/3G/4G/5G) into intelligent service hubs that are capable
of delivering highly personalized services (IT and cloud computing capabilities)
directly from the very edge of the network within the radio access network (RAN)
while providing the best possible performance in mobile networks [12]. Some
typical use cases of MEC are as follows:
• Intelligent video acceleration service
• Active location-aware application services
• Video stream analysis and video delivery optimization using data caching
• Augmented and virtual reality services
• RAN intelligence for customer experience
• Mobile PBX for large enterprises
• Connected vehicles and IoT gateway services
Examples of some leading MEC solution providers include the Vasona Smart
AIR platform, Saguna Open-RAN, Brocade MEC Platform Services, Nokia Liquid
Radio Applications Cloud Server, and Intel’s Network Edge Virtualization (NEV)
SDK MEC application and services.
The major components of the ETSI-MEC architecture [13] are summarized in
Table 1.1.

1.3.1.2 Internet of Things: Smart Grids and Smart Cities

Internet of Things: The Internet of Things (IoT) is the network of networks where
billions of devices/objects connect to each other and create new opportunities and
challenges. IoT ecosystem includes any type of devices/technology (smartphones,
connected cars, wearables, robots, vertical applications) that can connect to the
Internet. The International Telecommunication Union (ITU) Telecommunication

Table 1.1 The major components and its functionalities of the ETSI-MEC reference architecture
Components Description
Mobile-edge Sets the policy and configuration rules (e.g., traffic rules) for forwarding user
platform plane traffic to MEC applications. It also provides a set of services and access
to persistent storage
Mobile-edge Maintains an overall view of the deployed mobile-edge hosts, validates
orchestrator applications rules and requirements, and selects appropriate mobile-edge hosts
for instantiating a MEC application
Mobile-edge Responsible for life cycle management of applications and provides element
platform management functions to the mobile-edge platform
manager
Virtualized Responsible for managing, allocating, and releasing the resources of the
infrastructure virtualized infrastructure and also does rapid provisioning of applications
manager
Mobile-edge Runs on the top of the virtualized infrastructure provided by the mobile-edge
applications host and also interacts with mobile-edge platform to provide services
1 The Rise of Cloud Computing in the Era of Emerging Networked Society 11

Table 1.2 Overview of functional requirements of the IoT

Functional requirements Description
Application support Programmable interfaces, group management, time synchronization,
requirements collaboration, authentication, authorization, and accounting
Service requirements Service level agreements (SLAs), autonomic service provisioning,
service composition, service mobility, user mobility and device
mobility, virtual storage, and processing capabilities
Communication Heterogeneous communications (wired or/and wireless technologies,
requirements such as controller area network (CAN) bus, ZigBee (IEEE 802.15.4),
Bluetooth (IEEE 802.15.1), Wi-Fi (IEEE 802.11a/b/g/n/ac), 4G
LTE/LTE-Advanced, 5G), Low power Wireless Personal Area
Networks (IEEE 802.15.4/6LoWPA), communication modes
(event-based, periodic, and automatic communication modes),
autonomic networking (self-configuring, self-healing,
self-optimizing, and self-protecting capabilities), and context- and
location-aware communications
Device requirements Remote monitoring, control and configuration of devices, monitoring
of things, and device mobility
Data management Integrity checking and life cycle management of data; storing,
requirements aggregating, transferring, and processing the data; access control of
data; and high availability and reliability of data of things
Security and privacy Trust and privacy, mutual authentication and authorization between
protection requirements the devices, integration of security policies and techniques, and
security audit

Standardization Sector (ITU-T) in Recommendation ITU-T Y.2066 [14] defined

the IoT as a global infrastructure for the information society, enabling advanced
services by interconnecting (physical and virtual) things based on existing and
evolving interoperable information and communication technologies. IoT has an
enormous potential to bring innovations to new business. For instance, McKinsey
report shows that the IoT has the potential to create economic impact of $2.7–
$6.2 trillion annually by 2025. Some of the most promising uses are in healthcare,
infrastructure, and public sector services [3].
Tables 1.2 and 1.3 summarize the IoT functional (related to the IoT actors28 ) and
nonfunctional requirements (related to the implementation and operation of the IoT)
[14]. Even though cloud computing and IoT are two very different technologies,
both can be converged, giving rise to so-called IoT-cloud computing – a novel
paradigm and enabler for vast majority of large-scale application deployments.
Indeed, the convergence of cloud computing and IoT enables ubiquitous sensing
services and powerful computing platforms with large-scale computing and storage
capabilities, thus stimulating new innovations in the area of IoT.

28
Actors are external to the IoT and interact with the IoT.
Exploring the Variety of Random
Documents with Different Content
jetzt als praktisch bewährte Einrichtungen erfand — bedeutende sind
und der unzählige Male mit Wort und Schrift für dasselbe begeistert
und viele Andere begeisternd eintrat und wahrhaft unermüdlich
wirkte. Es ist dies der Kaufmann und Turngeräthefabrikant Herr
Oswald Faber in Leipzig,[2] dessen Bild als Zugführer der
Turnerfeuerwehr wir auf dem Titelblatt und im Text unsres Heftes VI
bringen. In wahrhafter Bescheidenheit hat er sich stets allen
Ovationen für seine Thätigkeit entzogen, ihm gebührt ein Ehrenplatz
in dieser Chronik unsres Leipzigs.
[1] Nach Oswald Fabers »Die freiwilligen Feuerwehren,« 3.
Auflage.
[2] Mit seiner Concurrenzarbeit »Ueber Organisation von Dorf-
Feuerwehren« mit der großen silbernen Medaille der k. k.
österreich. Regierung prämirt im Juli 1870 auf dem 8. deutschen
Feuerwehrtag zu Linz.

C. Die Rettungscompagnie.
Die Leipziger freiwillige Rettungscompagnie, welche neben der
städtischen und der Turnerfeuerwehr bestand, rekrutirte sich aus
Leipziger Bürgern und Einwohnern von den besten
Gesellschaftsklassen herab bis zum Arbeiterstande. Ein sehr großer
Theil derselben waren ebenfalls noch aktive oder doch frühere
Turner. Die Compagnie, deren Zusammensetzung, Ziele u. s. w. so
ziemlich dieselben waren, wie die der Turnerfeuerwehr, wich an der
Bekleidung insofern von der Turnerfeuerwehr ab, als sie dunklere,
schwarzgraue Blousen mit dem auf die Brustseite angestepptem R.
C. trug. Obwohl die Mitglieder derselben ebenfalls zum Spritzen- und
Steigerdienst vollständig ausgebildet waren und ihre eigene vom
Rath beschaffte Spritze besaßen, war ihr Augenmerk doch in erster
Linie, wie schon ihr Name sagt, auf das Rettungswerk von Personen
und beweglichem Besitzthum gerichtet. Die Rettungscompagnie,
welche eine Stärke von etwa 100 Mann besaß, wechselte mit der
Turnerfeuerwehr behufs Besetzung der Wache im Brühl dergestalt
ab, daß sie, nachdem die 15 tägigen Wachtposten der
Turnerfeuerwehr beendet waren, ihrerseits nun während 9 Tagen die
Wache besetzte, worauf wieder der Turnus der ersteren begann.
Auch die Rettungscompagnie nahm an der Tilgung aller Brände
während der Zeit ihres Bestehens mit gleicher Bravour und großer
Pflichttreue und Erfolg Theil und hielt — kleine Häkeleien dann und
wann ausgenommen — mit der Turnerfeuerwehr treue
Kameradschaft. Aber dieselben Gründe, welche schon 1871 eine
freiwillige Auflösung der Turnerfeuerwehr herbeiführten, führten auch
obwohl mehr als ein Jahrzehnt später ihre freiwillige Auflösung
herbei. Dieselbe erfolgte am 31. Dezember 1886. Bei dem
Abschiedscommers im alten Schützenhause am Abend des 31.
December wurde die gesammte Mannschaft zur Tilgung eines
größeren Feuers nach Reudnitz commandirt. Commandanten der
Rettungscompagnie waren nach einander:
Kaufmann Rudolf Gruner (s. Bericht an den Rath vom
5. August 1842).
Advokat (späterer Stadtrath) Schilling vom 5. April 1851
(ausgetreten am 1. Februar 1862).
Eisengießereibesitzer Gustav Götz vom 12. Februar 1862
(ausgetreten am 17. Februar 1870).
Kaufmann Hermann Meister, vom 23. Februar 1870; (vom
1. Juni 1875 städt. Branddirektor).
Zimmermeister Aug. Kersten (vom 5. Juni 1875, gest. im
August 1883).
Baumeister W. Rob. Rost (vom 12. Oktober 1883 bis zur
Auflösung der Compagnie am 31. Dezember 1886).
Beide Corporationen wurden vielen Hunderten freiwilliger
Feuerwehren in ganz Deutschland zum Vorbild, sie nahmen unter
allen derselben den ältesten und berechtigsten Vorrang ein und
wenn jetzt noch das — namentlich für kleinere und mittlere
Gemeinden von so außerordentlich wichtigen, werthvollen und mit
verhältnißmäßig geringem Kostenaufwande verbunden — freiwillige
Feuerlöschwesen in so hoher Blüthe steht, so fällt ein guter Theil
des Bewußtseins, wesentlich hierzu beigetragen zu haben, auf die
ehemalige freiwillige Feuerwehr zu Leipzig.
 XXXIII.
Auf der Wache der Turnerfeuerwehr.
Das Wachtlokal der Turnerfeuerwehr und Rettungscompagnie
befand sich bis zur Auflösung beider Corporationen im Brühl, Ecke
der Göthestraße, damalige städt. Fleischhallen und zwar in
ursprünglich zum Verkaufsgewölbe eingerichteten Räumen. Groß
war dasselbe nicht und von übermäßigem Comfort war darin keine
Rede. Im Hintergrund des ziemlich tiefen, aber nicht sehr breiten
Lokals befanden sich nebeneinander die »Pfefferkuchen« vulgo
»Matratzen« auf den Holzpritschen, auf denen des Schlafes
bedürftige Wachtmannschaften sich ausstrecken und der Ruhe
pflegen konnten, falls sie nicht die »Wache« hatten oder gar die
Wache allarmirt wurde. Ein einfacher großer Holztisch und mehrere
Stühle, eine Stechuhr zur Controlle der Wachthabenden, an den
Wänden Pflöcke und Kleiderhalter und eine alte Wanduhr, dies war
die ganze Einrichtung der »freiwilligen Wache.« Das Allarmiren nun
ging früher, ehe die Wachtlokale mit der Polizeiwache telegraphisch
verbunden waren, allerdings nicht ohne wirklichen Allarm vor sich.
Da stürmten die Feuerglocken von den Thürmen, die Trommeln der
Communalgarden rasselten durch die Straßen und die Feuersignale
ertönten aus den Hörnern der Signalisten der Garnison und bei
Nacht erschollen in diesen Chaos von Tönen noch der dumpfe Ton
der Nachtwächterhörner, feuerrufende Menschen rannten durch die
Straßen und von allen Seiten jagten Spritzen und Zubringer,
Sturmfässer und Geräthewagen dem Ziele zu, welches von den
Thürmern durch Herausstecken von Fahnen oder bei Nacht von
Laternen als die Gegend, in welcher das Feuer ausgebrochen war,
angedeutet wurde. Die zuerst am Brandplatz ankommende Spritze
wurde prämiirt und diese Prämie haben sich die beiden freiwilligen
Corps oft genug errungen. Waren doch ihre Mannschaften mit Leib
und Seele bei der Sache und trotz des meist heiteren, geselligen
Lebens, welches sich stets auf diesen Wachen entwickelte, stand
dieselbe stets auf dem Sprunge, ihre übernommenen Pflichten auch
voll und ganz auszuführen. Daß hierbei einige Mal sogar ein
Uebereifer zu Tage trat, ist wohl entschuldbar. So hatten junge
Mannschaften des 2. Zuges, die sich Nummer und Farbe ihrer
Spritze noch nicht genau eingeprägt hatten, einst das Malheur, bei
Feuerlärm einst am hellen Tage, statt ihrer Spritze, die der
Rettungscompagnie aus dem gemeinschaftlichen Depôt an der
ersten Bürgerschule zu ziehen und mit Unterstützung einiger
hilfsbereiter Lehrbuben und Gesellen im vollen Lauf nach der
Brandstelle zu fahren und dort in Thätigkeit zu setzen. Und —
welche Freude! — ihre Spritze war die erste am Platze und erhielt
die Prämie! — Aber — welche Enttäuschung, welche Spötteleien
und gegenseitigen Vorwürfe, als das Versehen erkannt wurde und
nun die Prämie der Rettungscompagnie zufiel! —
Beim Commers, nach Legung des Grundsteines zum Denkmal
für die Völkerschlacht (Anno 1863 — Gott weiß, wann das Denkmal
selbst erbaut wird) sang die Turnerfeuerwehr:
Wir und die Rettungscompagnie —
Sahn oftmals uns kaum an
Und dennoch hatten wir uns nie
Etwas zu Leid gethan.
Woraus der Streit entstanden war,
Ist Keinem recht bekannt
Und doch verging so manches Jahr —
Eh’ er sein Ende fand etc. etc.

Für alle Theilnehmer an diesen Wachen bildeten dieselben ein

Vergnügen, und den Werth und die Bedeutung derselben für das
kameradschaftliche Wesen lernte man eigentlich erst richtig
erkennen, als man in der letzten Kneiperei der Turnerfeuerwehr am
22. Juli 1871 unter anderen Schwanen-Gesängen auch den Vers
sang:
Nachdem zuvor im Tageblatt
Die Gründe dargelegt man hat —
Verschied zwar sanft — und dennoch schwer —
Die Leipz’ger Turnerfeuerwehr!
 Männer der besten Gesellschaftsklassen, aber auch einfache
Gesellen und Handwerker gehörten der Truppe an und alle verband
das Gefühl echter kameradschaftlicher Freundschaft. Daß natürlich
die Wachen der beiden Corps von den Wachen der berufsmäßigen
Feuerwehr insofern bedeutend abwichen, als dieselben eben von
den betreffenden Mannschaften mit Vergnügen bezogen und
»abgeschraubt« wurden, ist selbstverständlich, und nicht nur ein
geselliges, sondern auch oft genug ein feuchtfröhliches Treiben, so
weit solches mit den übernommenen Pflichten vereinbar war, machte
sich geltend. Scat und der solidere Schafkopf traten in ihr volles
Recht und wurden weidlich »gedroschen«, oft aber waren auch
Gäste »auf Wache«, die sich nicht »lumpen« ließen und zur
allgemeinen Erheiterung mit beitrugen. An Letzterer fehlte es aber
auch so nicht und so flog die Zeit von Abends 8 bis 2 Uhr vorüber.
Erst um diese Zeit, wo die sogenannte »Hundewache« (von 2—4)
begann, machte sich die Ermüdung geltend und die gefürchteten
»Pfefferkuchen« (Matratzen) wurden aufgesucht. Gefürchtet aber
waren diese Schmerzenslager wegen der Unmasse jener schwarzen
Eindringlinge, die sich sogar oft genug bis zu Quälgeistern unsrer
Damenwelt aufschwingen und also für den robusten Körper eines
Feuerwehrmannes nicht die Spur von Achtung oder Nachsicht
hatten. Das hopste und sprang lustig umher und zwickte und
zwackte, daß männiglich nicht die zartesten Redensarten den
Sprechwerkzeugen der also Gefolterten entquollen.
»Donnerwetter!« schrie einst, früh gegen 3 Uhr, als der
Wachtcommandant, noch allein munter, bei der Stechuhr saß und
las, ein Wehrmann und sprang mit gesträubtem Haar und einem
neuen Fluche vom »Pfefferkuchen« herab.
»Was ist denn los?« rief erschrocken der Lesende.
»Donnerwetter« rief der Andere, seines Zeichens ein biederer
Tanzlehrer, wieder und griff nach seinem Helm, als wollte er die
Wache verlassen, »e Scorpion — e Scorpion hat mich gebissen —
ich gehe heem!«
Der Wachtcommandant hatte alles Mögliche zu thun, ja mußte
zuletzt seine ganze Autorität aufbieten, um den Aufgeregten zu
beruhigen, der dabei blieb »e Scorpion« habe ihn gebissen.
Auch die anderen Mitglieder der Wache waren munter
geworden und eine allgemeine Durchsuchung der »Pfefferkuchen«
begann. Hei! wie das fröhlich hüpfte und sprang — und — man fand
zwar keinen Scorpion — aber ein so riesiges Exemplar der Familie
»Floh« wurde trotz der zu solchen Fängen nur wenig geschickten
Hände der tapferen Turner gefangen und hingerichtet, daß es auf
dem Tisch ordentlich »knallte« und es kein Wunder war, wenn der
Jünger Terpsichores an einen Scorpion gedacht hatte. — —
Jedem von denen, die als Gäste einen solchen Wachtabend mit
verleben durften, wird derselbe sicher unvergeßlich sein und
manche bethätigten ihre Dankbarkeit dafür, daß sie der Wache
»etwas stifteten«.
So hatte sich einst ein Meßfremder aus Nordhausen auf der
Wache so gut amüsirt, daß er versprach, der Wache ein Fäßchen
Nordhäuser — aber echten und alten — zu schicken. Aber als
dieselbe Mannschaft nach 15 Tagen wieder auf Wache kam, fragten
sie vergeblich nach dem Fäßchen und man lachte schließlich über
das windige Versprechen. Wie ward aber den Guten zu Muthe, als
sie bald darauf erfuhren, daß das Fäßchen allerdings richtig
angekommen war, aber an einem von der Rettungscompagnie
besetzten Abend, und da das Geschenk eben einfach an die
»freiwillige Wache« adressirt war, so hatten sich die von der
Rettungscompagnie nicht als Verächter der von einem »Pirnschen«
gegebenen edlen Gottesgabe bewiesen und den Inhalt des
Fäßchens zur allgemeinen, tiefgefühlten Entrüstung der Anderen —
bis auf die Nagelprobe geleert. Ja — ja:
Wir und die Rettungscompagnie u. s. w.

Und die — waren doch so unschuldig — so unschuldig. — Der

Nordhäuser wurde aber als »ausgezeichnet« von ihnen gepriesen —
nicht gerade zur Beruhigung der Anderen.
 Auf der Wache der Turnerfeuerwehr.
Manche alten Kämpen der Turnerfeuerwehr und
Rettungscompagnie werden frühere Mitglieder der beiden Corps auf
unserem Bilde erkennen. Viele — viele von ihnen sind längst
schlafen gegangen.
Es ist nicht zu leugnen, daß sich mit der Neuorganisation der
Leipziger Feuerwehr zu einem möglichst organischen Ganzen, sich
die Wache der freiwilligen Wehren allmälig als überflüssig — ja
vielleicht sogar der allgemeinen Verwaltung — hinderlich erwies und
so kam es denn, daß im Laufe der Zeit Zustände eintraten, bei
denen die freiwilligen Wehren fühlen mußten, daß sie — entbehrlich
waren und dies höheren Ortes längst anerkannt wurde. Das Beste
wäre nun wohl gewesen, wenn man dies einfach und offen den
Corps mitgetheilt hätte, statt dessen — und dies wohl wieder, weil
man ihre früheren großen Dienste eben ganz und voll anerkannte —
suchte man durch kleinliche Manöver mancher Art die Corps zu
veranlassen, selbst zu gehen, und als dies denn endlich geschah,
konnte man sich nicht wundern, daß Gefühle bitterer
Enttäuschungen und Zurücksetzungen mit zum Ausbruch kamen,
wenn auch nur innerhalb der letzten Versammlungen und geselligen
Feste der Corps selbst.
Der Rath schrieb auch »Ich danke schön,
Es ist schon gut — der Mohr kann geh’n —
Gebt möglichst bald — am liebsten gleich,
Die Blousen ab — und Euer Zeug!«

D’rauf streckten alle das Gewehr —

Mit Gurten, Flechen, Beilen schwer,
Beladen sah man Manchen hin —
Zu Brutus — unserm Hausmann zieh’n! u. s. w.

sangen sie wehmüthig im letzten Commers am 22. Juli 1871 und

daß man sie zwang freiwillig zu gehen, kam in den Versen eines
anderen Liedes bei jenem Commers so recht schmerzlich zum
Ausdruck. Da hieß es unter Anderem:
Der junge Baum, den in die Erde —
Wir voller Hoffen einst gesenkt,
Daß er ein Waldeskönig werde —
Hat reiche Freude uns geschenkt.

Er bot dem Wetter Trotz, der Starke,

Und seine Krone brach kein Sturm —
Nun aber nagt an seinem Marke,
An seiner Lebenskraft der Wurm.

Und soll er lange kläglich siechen

Wehrlos des gier’gen Wurmes Raub —
Und endlich doch am Boden liegen
Mit dürrem Ast — und welkem Laub?
— Nein — dreimal Nein! Die letzte Liebe
Gewährt ihm noch und zaudert nicht —
Daß von der Axt und ihrem Hiebe
In voller Pracht er niederbricht!
 Mehr als zwanzig Jahre sind seitdem verflossen, aber die
Geschichte der freiwilligen Turnerfeuerwehr und der etwas später
ebenfalls aufgelösten Rettungscompagnie ist mit der Leipzigs eng
verflochten geblieben und den beiden Corps gebührt für immer ein
Ehrenblatt in der Chronik unserer Vaterstadt.
 Inhalts-Verzeichniß.

Heft 1.
Vorrede des Verfassers 3
Die alte innere Stadt anno 1840 5
Heiterer Rückblick auf die Steuerbeitreibung in früherer Zeit (mit Bild.) 12
Die Südvorstadt. — Ein Sonntagsausflug vor 50 Jahren 20
Das Gutenbergfest 1840 25
»Die Communalgarde rückt aus!« (mit Bild) 29

Heft 2.
Der »hohe Seeler!« 41
Kramerlehrling und Gehilfe (mit Bild) 47
Verschiedene Chronica’s von 1840—1845 58
Die letzte öffentliche Hinrichtung in Leipzig 64
Die Leipziger Sänftenträger-Compagnie (mit Bild) 71
D. L. M. 64

Heft 3.
Allerlei Chronica von 1846—49 81
Die innere Stadt zur Meßzeit vor 40 Jahren (mit Bild) 87
Der damalige Meßfremde 94
Wichsekrah (mit Bild) 98
Student und Verbindungströdeljude 108
Ein Abend bei den Harfenistinnen in Auerbachs Keller vor 40 Jahren
(mit Bild) 115

Heft 4.
Allerlei Chronica von 1850—1859 129
Die Hiersemusen! (mit Bild) 135
Der Judenbrühl 143
Unter den Buden (mit Bild) 150
Die Leipziger Meßmusikanten und das Tagebuch des Chorführers und
Leinewebers Gottfried Hahn aus Stollberg im sächs. Erzgebirge (mit
Bild) 156

Heft 5.
Allerlei Chronica von anno 1860 169
Eckensteher und Nachtwächter vor 40 Jahren (mit Bild) 171
Der alte Petersschießgraben (mit Bild) und Leipziger Originale: Dr. Ewald 180
Leipzigs Südosten vor 40 Jahren 186
In Wechselhaft (mit Bild) 193
Der Verbrechertisch in der »guten Quelle« (mit Bild) 206

Heft 6.
Allerlei Chronica 217
Die politische Lage Deutschlands zu Ende der fünfziger, bis Mitte der
sechziger Jahre des 19. Jahrhunderts 219
Das 3. deutsche Turnfest 1863 (mit Bild) 224
Feier der Völkerschlacht 1863 239
Leipzigs frühere Feuerwehrverhältnisse 241
Auf der Wache der Turnerfeuerwehr (mit Bild) 254
 Verlag von Otto Lenz in Leipzig.
Bibliothek niederdeutscher Werke:
Bd. 1. Frans Essink, sien Liäwen un Driewen äs aolt Mönstersk Kind. Von
Prof. Dr. H. Landois, 1. humor. Teil: Bi Liäwtieden. 7. Aufl., illustriert. brosch.
M. 3.—, elegant geb. M. 4.—
Bd. 2. Frans Essink. 2. satyr. Teil: Nao sienen Daud. 6. Aufl., illustriert, brosch.
M. 1.80, elegant geb. M. 2.70.
Bd. 3. Frans Essink. 3. romant. Teil: Up de Tuckesburg. Brosch. M. 4.—, geb. M.
5.—.
Bd. 4. Sappholt aus Westfalens Dichterhain oder Mirza Schaffy in Holsken.
Neue humor. plattdeutsche Gedichte von Tonius Happenklang. Mit
Illustrationen, brosch. M. 1.40, elegant geb. M. 2.25.
Bd. 5/6. De westfölsche Husfrönd. Allerlei Spinnstuowen­geschichten von Karl
Prümer. Bd. 1/2. brosch. à M. 1.80, geb. à M. 2.70.
Bd. 7. Rugge Wiäge. Aus dem westfälischen Bauernleben in niederdeutscher
Sprache erzählt von Ferdinand Krüger. 3. Ausgabe, brosch. M. 2.—, eleg.
geb. M. 2.80.
Bd. 8. Dä Chronika van Düöpm. Ernste und spassige Epistel mit allerlei schäune
Biller von Karl Prümer, brosch. M. 1.80, elegant geb. M. 2.70.
Bd. 9. Plattdütsche Lachpillen oder lustige Reimereien in der Mundart der
Kanonen- und Kohlenstadt Essen von Willem Täpper in Bochum. Bd. 1. 3.
Auflage. Brosch. M. 1.20, eleg. geb. M. 2.10.
Bd. 10/13. — — Band 2/5 erscheinen später.
Bd. 14/16. Hempelmann’s Smiede. Ein westfälischer Roman aus der »guten
alten Zeit« in münsterländisch-niederdeutscher Sprache von Ferdinand
Krüger. Bd. 1/3. brosch. à M. 3.—, geb. à M. 4.—

Weitere empfehlenswerthe Werke:

Frl. Paulinchen Huhn’s Briefe an ihre Freundin Frl. Laura Niedlich. brosch. Mk.
3.—, eleg. geb. Mk. 4.—
»Cabinetstücke psychol. Feinmalerei« (Lpzg. Tagebl.) — »erinnert an
Raabe’s Chronik der Sperlingsgasse« (Allg. Modenztg.) — »ergötzl. Bild
kleinstädt. Lebens« (National-Ztg.) »für die »Buchholzen« Schwärmende wird
das echten Berliner Humor enthaltende Buch sehr zusagen.« (Für’s Haus)
u. s. w.
Blumensprache nebst Liedern der Liebe. 15. Aufl., brosch. M. —.75, geb. 1.25.
Die Verlagshandlung Otto Lenz in Leipzig, Gellertstr. 16.
 Weitere Anmerkungen zur Transkription
Offensichtliche Fehler wurden stillschweigend korrigiert. Die Darstellung der
Ellipsen wurde vereinheitlicht.
Korrekturen:
Prinzipal → Principal (häufigere Verwendung)
S. 54: Da jeder Principal genau wußte
Peterstraße → Petersstraße (es gibt keine Peterstraße in Leipzig)
S. 7: links von der Petersstraße
S. 9: Die Petersstraße, damals noch
S. 80: Leinenwaarengeschäft der Petersstraße
S. 84: Petersthor und Petersstraße
S. 162: in der Petersstraße
 *** END OF THE PROJECT GUTENBERG EBOOK
ERINNERUNGEN EINES ALTEN LEIPZIGERS ***

Updated editions will replace the previous one—the old editions

will be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States copyright
in these works, so the Foundation (and you!) can copy and
distribute it in the United States without permission and without
paying copyright royalties. Special rules, set forth in the General
Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the

free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree to
abide by all the terms of this agreement, you must cease using
and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only

be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project
Gutenberg™ works in compliance with the terms of this
agreement for keeping the Project Gutenberg™ name
associated with the work. You can easily comply with the terms
of this agreement by keeping this work in the same format with
its attached full Project Gutenberg™ License when you share it
without charge with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.

1.E. Unless you have removed all references to Project

Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project
Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United

States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it
away or re-use it under the terms of the Project Gutenberg
License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country where
you are located before using this eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is

derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of the
copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is

posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files
containing a part of this work or any other work associated with
Project Gutenberg™.
 1.E.5. Do not copy, display, perform, distribute or redistribute
this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must, at
no additional cost, fee or expense to the user, provide a copy, a
means of exporting a copy, or a means of obtaining a copy upon
request, of the work in its original “Plain Vanilla ASCII” or other
form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or

providing access to or distributing Project Gutenberg™
electronic works provided that:

• You pay a royalty fee of 20% of the gross profits you derive from
the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and

personal growth!

textbookfull.com