Lecture 4 Slides

Information & Communication
Architecture 2 [BINF 405]
GUC - Spring 2024 – Lecture 4

Cloud Computing
Dr. Ayman Al-Serafi
TAs: Ghada Ahmed, Tameem Alghazaly, Youssef Ihab, Mohab Gehad

Outline
1. Introduction to Cloud Computing
2. Types of Cloud Computing
3. Business Analysis of Cloud Computing
4. Conclusion
Q&A breaks
between sections
Urgent Qs only in
between!
ICA II - GUC - Dr. Ayman Alserafi 4-2
Outline
4. Conclusion

Information & Communication Architecture
Components

Local Area
Network (LAN) Server-client
hosted inside LAN inside
company company
Gateway to the Wide

Area Network (WAN) of
Internet. Makes local
applications available to
external and public
“clients” over Internet.
All applications hosted on

the Internet (web servers)
and accessible by any
computing device! No
hardware / software hosted
on-premise inside company.
Companies rent computing
power as a service from 3rd
party service providers.

Cloud Computing
• All clients are thin clients
• All applications stored on application

servers connected to the Internet
• Client gets application logic and data

stored remotely on a distributed
computing network over the Internet
• Web Services (Web-based SaaS –

Software as a service)
• Computer-to-computer use of the
Internet
• cloud computing (Internet as
hub)
• “In-house” computing a thing
of the past

In the spot light
 “… nearly half of large enterprises will have hybrid cloud
deployments by the end of 2017 ...”.
Source: http://www.gartner.com/newsroom/id/2613015
 By 2016, poor return on equity will drive more than 60 percent of
banks worldwide to process the majority of their transactions in the
cloud.
Source: http://www.gartner.com/newsroom/id/2607115
 By 2019, more than four-fifths (86 percent) of workloads will be
processed by cloud data centers; 14 percent will be processed by
traditional data centers.
Source: http://www.cisco.com/c/en/us/solutions/collateral/service-provider/global-cloud-index-
gci/Cloud_Index_White_Paper.html
ICA II - GUC - Dr. Ayman Alserafi 7

In the spot light

In the spot light

What is Cloud Computing?
 Cloud computing, the long-held dream of computing
 Computing capabilities without upfront costs of infrastructure!
 Cloud computing refers to both the applications delivered as services over the Internet
and the hardware and systems software in the data centers that provide those services.
The services themselves have long been referred to as Software as a Service (SaaS).
 Some vendors use terms such as IaaS (Infrastructure as a Service) and PaaS (Platform as
a Service) to describe their products, but we look into these later because accepted
definitions for them still vary widely.
 The National Institute of Standards and Technology (NIST) defines
cloud computing as:
 “a model for enabling convenient, on-demand network access to a shared
pool of configurable computing resources (for example, networks, servers,
storage, applications, and services) that can be rapidly provisioned and
released with minimal management effort or service-provider interaction”
 Cloud Computing is a general term used to describe a new class of network based
computing that takes place over the Internet, basically a step on from Utility
Computing.
 These platforms hide the complexity and details of the underlying
infrastructure from users and applications by providing very simple graphical user
interface (GUI) or API (Applications Programming Interface).

Users & providers of cloud computing

Cloud-based software services
Software as a service (SaaS):
• Accessed with web browser over internet
• Users pay on subscription or per-transaction, e.g. Salesforce.com
• Service Level Agreements (SLAs): formal agreement with service

providers
• Examples: e-CRM, www.salesforce.com; MS office 365

Key Characteristics
 A number of characteristics define cloud data,
applications services and infrastructure:
 Remotely hosted:
 Services or data are hosted on remote infrastructure.
 Ubiquitous:
 Services or data are available from anywhere.
 Commodified:
 The result is a utility computing model similar to that of traditional
utilities, like gas and electricity - you pay for what you would want!

Cloud computing - Features
 Agility – On demand computing infrastructure
 Linearly scalable – challenge
 Reliability and fault tolerance

 Self healing – backups, etc
 SLA driven – Policies on how quickly requests are processed via service level
agreement
 Virtualized – decoupled from underlying hardware. Multiple applications

can run in one computer
Next lecture
 Data, Data, Data

 Distributing, partitioning, security, and synchronization
Big Data

Public versus private cloud
 A company uses computing infrastructure provided by a 3rd party
over the cloud (if public) or provided by a geographically
distributed location of the same company (if private cloud)
 The datacenter hardware and software is what we will call a cloud.

 A datacenter is a group of connected servers storing data and applications, connected over a network
and located at a single location.
 When a cloud is made available in a pay-as-you-go manner to the general

public, we call it a public cloud; the service being sold is utility computing.
 Pay-as-you-go means that the cloud computing user pays only for the utilized computing resources
according to actual usage (as per business need arise)
 We use the term private cloud to refer to internal data centers of a business or other
organization, not made available to the general public, when they are large
enough to benefit from the advantages of cloud computing.

Public, Private and Hybrid clouds

Cloud computing contracts
1. Pay per time of utilization of computing
resources
2. Pay per number of transactions
3. Pay per number of users
4. Pay per amount of storage and computing
processors
5. Pay per number of software features used
6. Pay per amount of bandwidth consumed
The amount of data

transfer between the
cloud computing user and
provider
Outline
4. Conclusion
Q&A
Cloud offerings [services]
SaaS
Software as a Service
PaaS
Platform as a Service
IaaS
Infrastructure as a Service

Cloud Anatomy
 Application (Software) Services:
 Gmail, GoogleCalender
 Payroll, HR, CRM etc
 Sugar CRM, IBM Lotus Live
 Platform Services:
 Middleware, Integration, Messaging,
Information, connectivity, programming
compilers and environment, etc
 AWS, IBM Virtual images, Boomi, CastIron,
Google Appengine, Microsoft Azure Platform
 Infrastructure as services:
 Full computer stack (Operating System and
kernel) access without pre-installed or
restricted platforms or software
  Most flexible cloud computing infrastructure!
 IBM Blue house, VMWare, Amazon EC2,, Sun
Parascale

Examples of Cloud Computing Types
Source: Luchette, J., Nelson, G.

K., McLane, C. F., & Cecan, L. I.
(2009, November). Unlimited
virtual computing capacity using
the cloud for automated
parameter estimation. In
Proceedings of the 1st PEST
Conference (pp. 1-16).

Example SaaS: Salesforce CRM

Example SaaS: Google Docs

SaaS for Microsoft Office

Types of Cloud Computing

Cloud Architecture Business
Applications
Development
Environment
Basic and
complete
hardware and
software
control

Classes of utility computing (IaaS)
 Our view is that different utility computing offerings will be
distinguished based on the cloud system software’s level of
abstraction and the level of management of the resources.
1. Amazon EC2 is at one end of the spectrum as IaaS. An EC2 instance

looks much like physical hardware, and users can control nearly the
entire software stack, from the kernel (operating system) upward.
This low level makes it inherently difficult for Amazon to offer
automatic scalability and failover because the semantics associated
with replication and other state management issues are highly
application-dependent.

Classes of utility computing (PaaS)
2. At the other extreme of the spectrum are application domain-
specific platforms such as Google AppEngine (PaaS), which is
targeted exclusively at traditional Web applications. AppEngine’s
impressive automatic scaling and high-availability mechanisms,
and the proprietary MegaStore data storage available to
AppEngine applications, all rely on these constraints.
3. Applications for Microsoft’s Azure are written using the .NET

libraries, and compiled to the Common Language Runtime, a
language-independent managed environment. The framework is
significantly more flexible than AppEngine’s, but still constrains
the user’s choice of storage model and application structure.

Other forms [types] of services
 Storage-as-a-service
 Storage-as-a-service is a business model in which a company or
individual rent a storage / database infrastructure.
 Analytics-as-a-service (AaaS)
 Such cloud‐based real-time AaaS are able to render organizations
continuous analytics with Big Data and Artificial Intelligence hence
widen the innovation capacity even among SMB’s.

Example: Google Cloud
 Compute
 App Engine - Platform as a Service to deploy Java, PHP,
Node.js, Python, C#, .Net, Ruby and Go applications.
 Compute Engine - Infrastructure as a Service to run
Microsoft Windows and Linux virtual machines.
 Storage & Databases

 Cloud SQL - Database as a Service based on MySQL,
PostgreSQL and Microsoft SQL Server.
 Networking
 Cloud Armor - Web application firewall to protect
workloads from DDoS attacks.
 Cloud CDN - Content Delivery Network based on Google's
globally distributed edge points of presence.
 Big Data Source: Javatpoint

 BigQuery - Scalable, managed enterprise data warehouse
for analytics.
 Dataproc - Big data platform for running Apache Hadoop
and Apache Spark jobs.
Source: Wikipedia
Content Delivery Networks (CDNs)
United States
CDN is an umbrella term spanning
different types of content delivery
China services for websites and web
applications: video streaming,
Egypt software downloads, web and
mobile content acceleration,
Japan licensed/managed CDN,
transparent caching, and services
to measure CDN performance, load
balancing, Multi CDN switching and
Netherlands Germany analytics and cloud intelligence.
CDN vendors may cross over into
other industries like security, with
DDoS protection and web
Source: Thesis “Multi-Criteria Optimization of
application firewalls (WAF), and
Content Delivery within the Future Media WAN optimization.
Internet” by: Joachim Bruneau-Queyreix
Load balancing is distributing equally the requests

for content across distributed remote servers,
based on requesters location

Denial of Service Attack
A distributed denial-of-
service (DDoS) cyber-
attack is a malicious
attempt to disrupt the
normal traffic of a
targeted server,
service or network by
overwhelming the
target or its
surrounding
Attacker gets control of
multiple machines on the infrastructure with a
same network to fire multiple flood of Internet traffic.
concurrent requests at the (source: Cloudflare)
same time!

The Internet of Things
 All devices connected over the internet and communicate
autonomously to synchronise activities
 Depends on having sensors connected to the Internet
 Example: car can communicate with A.C. at home to turn on when
returning back home OR washing machine can communicate with
fridge to reduce electricity consumption!
 What is the danger of this system?
 Cyberwar can paralyze a whole city if hack the system or make a cyber-
attack on the infrastructure!
Source:
https://www.dotmagazine.online/issu
es/digital-infrastructure-
foundation/the-internet-of-the-
future/future-smart-city
Outline
4. Conclusion
Q&A
Why cloud computing?
 SCALABILITY: The appearance of infinite computing resources available on
demand, quickly enough to follow load surges, thereby eliminating the need for
cloud computing users to plan far ahead for provisioning.
 FLEXIBILITY: The elimination of an up-front commitment by cloud users,
thereby allowing companies to start small and increase hardware resources only
when there is an increase in their needs via pay-as-you-go approach
 ADAPTABILITY: The ability to pay for use of computing resources on a short-
term basis as needed (for example, processors by the hour and storage by the day)
and release them as needed, thereby rewarding conservation by letting machines
and storage go when they are no longer useful.
 BEST PRACTICE: The utilization of best practice and IT architectures from cloud
computing service providers without the need for having internal experts or
qualified system architects
 Example: Denial of Service attacks (DoS) prevention by monitoring and filtering client requests
using web application firewall
 ECONOMIES OF SCALE: Lowers costs to run data and computing centers due to
economies of scale, due to virtualization of resources to fully utilize them efficiently!

Why NOT cloud computing?
 SECURITY: Data privacy and security depends on the security
measures of 3rd party service provider
 Data privacy might be at risk
 LOSS OF CONTROL: Company does not own the applications or its
data, thereby cloud computing companies have more control and power
over client’s data and infrastructure, in addition to dependency of 3rd party
service uptime and inability to respond to failures.
 VENDOR LOCK-IN: The cloud computing company can prevent the
client from migrating to another provider which can put a burden on the
organization and prevent upgrading to other technologies, and company
will be at mercy of the service prices stipulated by the service provider.
 Example: preventing migration of data except after expensive migration
“consultation” fees
 AUDITING DIFFICULTIES: If the service provider does not provide
capabilities to track usage of the system and to audit transactions, then it
will be difficult to govern the IT infrastructure.
 BAD INFRASTRUCTURE OBSTACLES: if there is a slow internet
connection or low bandwidth to upload data, it will be restricting the
computing capabilities.

10 Obstacles & opportunities

1. Business continuity & service
availability
 Just as large Internet service providers use multiple network
providers so that failure by a single company will not take them off
the air, we believe the only plausible solution to very high
availability is multiple cloud computing providers. Table 3
shows recorded outages for Amazon Simple Storage Service (S3),
AppEngine and Gmail in 2008, and explanations for the outages.

2. Data lock-in
 Software stacks have improved interoperability among platforms, but the
storage APIs for cloud computing are still essentially proprietary, or at least
have not been the subject of active standardization. Thus, customers cannot
easily extract their data and programs from one site to run on another.
 One solution would be to standardize the APIs in such a way that a SaaS
developer could deploy services and data across multiple cloud computing
providers so that the failure of a single company would not take all copies of
customer data with it.
Make sure contractual

terms allow for
unlimited / unrestricted
API access to data!

3. Data confidentiality/auditability
 Cloud users face security threats both from outside and inside the cloud.
Many of the security issues involved in protecting clouds from outside
threats are similar to those already facing large data centers. In the cloud,
however, this responsibility is divided among potentially many parties,
including the cloud user, the cloud vendor, and any third-party vendors that
users rely on for security-sensitive software or configurations. The cloud
user is responsible for application-level security. The cloud provider is
responsible for physical security, and likely for enforcing external firewall
policies.
 The primary security mechanism in today’s clouds is virtualization. It is a
powerful defense, and protects against most attempts by users to attack one
another or the underlying cloud infrastructure. However, not all resources
are virtualized and not all virtualization environments are bug-free.
 One last security concern is protecting the cloud user against the provider.

4. Data transfer bottlenecks
 Applications continue to become more data-intensive. If we assume
applications may be “pulled apart” across the boundaries of clouds, this may
complicate data placement and transport. At $100 to $150 per terabyte
transferred, these costs can quickly add up, making data transfer costs an
important issue. Cloud users and cloud providers have to think about the
implications of placement and traffic at every level of the system if they
want to minimize costs. This kind of reasoning can be seen in Amazon’s
development of its new cloud front service.
 One opportunity to overcome the high cost of Internet transfers is to ship
disks. Jim Gray found the cheapest way to send a lot of data is to ship
disks or even whole computers. While this does not address every use case,
it effectively handles the case of large delay-tolerant point-to-point
transfers, such as importing large data sets.
 Ship 10TB from Berkeley to Seattle, WA using bandwidth of 20 Mbits/Sec
over WAN link would take 10*1012 bytes/(20*106 bits/sec)=4,000,000
sec which is 45 days. Whereas it could be shipped over night!
Or provide bigger
bandwidth connection!
5. Performance unpredictability
 Our experience is that multiple virtual machines (VMs) can share
CPUs and main memory surprisingly well in cloud computing, but that
network and disk I/O sharing is more problematic.
 One opportunity is to improve architectures and operating systems to

efficiently virtualize interrupts and I/O channels. Note that IBM
mainframes and operating systems largely overcame these problems in
the 1980s, so we have successful examples from which to learn.
Another possibility is that flash memory will decrease I/O
interference.
Make sure cloud service

provider has high reputation of
providing high quality services
and uptime!
6. Scalable storage
 The opportunity, which is still an open research
problem, is to create a storage system that would not
only meet existing programmer expectations in regard
to durability, high availability, and the ability to
manage and query data, but combine them with the
cloud advantages of scaling arbitrarily up and down on
demand.
Make sure whether there is a
maximum limit of allowed
storage capacity / bandwidth
or not?!

7. Bugs in large-scale distributed
systems
 One of the difficult challenges in cloud computing is
removing errors in these very large-scale distributed
systems.
 A common occurrence is that these bugs cannot be
reproduced in smaller configurations, so the debugging
must occur at scale in the production data centers.
Cloud service provider should provide a

testing environment beside the live /
production environment!

8. Scaling quickly
 Pay-as-you-go certainly applies to storage and to
network bandwidth, both of which count bytes used.
Computation is slightly different, depending on the
virtualization level.
 Google AppEngine automatically scales in response
to load increases and decreases, and users are
charged by the cycles used.
 AWS charges by the hour for the number of
instances you occupy, even if your machine is idle.
 The opportunity is then to automatically scale quickly
up and down in response to load in order to save
money, but without violating service level
agreements.

9. Reputation fate sharing
 One customer’s bad behavior can affect the reputation of others using the
same cloud.
 For instance, blacklisting of EC2 IP addresses by spam prevention services
may limit which applications can be effectively hosted. An opportunity
would be to create reputation- guarding services similar to the “trusted
email” services currently offered (for a fee) to services hosted on smaller
ISP’s, which experience a microcosm of this problem.
 Another legal issue is the question of transfer of legal liability—cloud
computing providers would want customers to be liable and not them (such
as, the company sending the spam should be held liable, not Amazon). In
March 2009, the FBI raided a Dallas data center because a company whose
services were hosted there was being investigated for possible criminal
activity, but a number of “innocent bystander” companies hosted in the
same facility suffered days of unexpected downtime, and some went out of
business.

10. Software licensing
 Users pay for the software and then pay an annual maintenance fee.
Indeed, SAP announced that it would increase its annual maintenance
fee to at least 22% of the purchase price of the software, which is
close to Oracle’s pricing. Hence, many cloud computing providers
originally relied on open source software in part because the licensing
model for commercial software is not a good match to utility
computing.
 The primary opportunity is either for open source to remain popular

or simply for commercial software companies to change their
licensing structure to better fit cloud computing. For example,
Microsoft and Amazon now offer pay-as-you-go software licensing for
Windows Server and Windows SQL Server on EC2. An EC2 instance
running Microsoft Windows costs $0.15 per hour instead of $0.10
per hour for the open source alternative.

Outline
4. Conclusion
Q&A
Date Lecture (Saturdays) Tutorials (in same week)
Week 1 Introduction to Information & Communication Architecture II
Intro + XML Lab

Week 2 Distributed Systems
Web APIs + HTTP Protocols Lab

Week 3 XML Intro + HTML + HTTP Protocol (Intro to VS and Webforms + XML Binding)
HTTP API Methods + Practical for HTTP methods
Week 4 Cloud Computing  Assignment 1
 Mini-Project 1
HTTP API Methods + Practical for HTTP methods
Week 5 Virtualisation
 Quiz 1
Week 6 Middleware Overview and components Cloud Computing Case Study
16 March –
Mid-Term Exam
1 April
Virtualization Case Study
Week 7 Middleware Overview and Components  Assignment 1 submission
 Mini-Project 1 submission
SOA, Web Services and SOAP
Week 8 The Organizational SOA Roadmap
 Assignment 2
Week 9 Registering and Discovering Web Services SOAP + WSDL + UDDI Lab
REST API Lab 1 +JSON
Week 10 REST API  Assignment 2 submission
 Quiz 2
Middleware Messaging, Enterprise Service Bus, REST API Lab 2
Week 11  Final Project submission
Transaction Processing
Final Course Lab
Middleware Messaging, Enterprise Service Bus,
Week 12  Quiz 3
Transaction Processing
 Assignment 2 submission
Week 13 Revision
28 May - 13 June
Final Exam
THANK YOU FOR
YOUR ATTENTION
NEXT WEEK: Virtualisation
NEXT TUTORIAL: Cloud

Computing Case Study

Lecture 4 Slides

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lecture 4 Slides

Uploaded by

Copyright:

Available Formats

Information & Communication

Architecture 2 [BINF 405]

GUC - Spring 2024 – Lecture 4

Dr. Ayman Al-Serafi

TAs: Ghada Ahmed, Tameem Alghazaly, Youssef Ihab, Mohab Gehad

ICA II - GUC - Dr. Ayman Alserafi 4-3

ICA II - GUC - Dr. Ayman Alserafi 4-4

Gateway to the Wide

All applications hosted on

ICA II - GUC - Dr. Ayman Alserafi 4-5

• All applications stored on application

• Client gets application logic and data

• Web Services (Web-based SaaS –

ICA II - GUC - Dr. Ayman Alserafi 4-6

ICA II - GUC - Dr. Ayman Alserafi 7

ICA II - GUC - Dr. Ayman Alserafi 8

ICA II - GUC - Dr. Ayman Alserafi 9

ICA II - GUC - Dr. Ayman Alserafi 10

ICA II - GUC - Dr. Ayman Alserafi 11

• Users pay on subscription or per-transaction, e.g. Salesforce.com

• Service Level Agreements (SLAs): formal agreement with service

• Examples: e-CRM, www.salesforce.com; MS office 365

ICA II - GUC - Dr. Ayman Alserafi 4-12

ICA II - GUC - Dr. Ayman Alserafi 4-13

 Reliability and fault tolerance

 Virtualized – decoupled from underlying hardware. Multiple applications

 Data, Data, Data

ICA II - GUC - Dr. Ayman Alserafi 14

 The datacenter hardware and software is what we will call a cloud.

 When a cloud is made available in a pay-as-you-go manner to the general

ICA II - GUC - Dr. Ayman Alserafi 15

ICA II - GUC - Dr. Ayman Alserafi 16

The amount of data

ICA II - GUC - Dr. Ayman Alserafi 4-19

ICA II - GUC - Dr. Ayman Alserafi 20

Source: Luchette, J., Nelson, G.

ICA II - GUC - Dr. Ayman Alserafi 4-21

ICA II - GUC - Dr. Ayman Alserafi 4-22

ICA II - GUC - Dr. Ayman Alserafi 4-23

ICA II - GUC - Dr. Ayman Alserafi 4-24

ICA II - GUC - Dr. Ayman Alserafi 25

ICA II - GUC - Dr. Ayman Alserafi 4-26

1. Amazon EC2 is at one end of the spectrum as IaaS. An EC2 instance

ICA II - GUC - Dr. Ayman Alserafi 27

3. Applications for Microsoft’s Azure are written using the .NET

ICA II - GUC - Dr. Ayman Alserafi 28

ICA II - GUC - Dr. Ayman Alserafi 29

 Storage & Databases

 Big Data Source: Javatpoint

Load balancing is distributing equally the requests

ICA II - GUC - Dr. Ayman Alserafi 4-31

ICA II - GUC - Dr. Ayman Alserafi 4-32

ICA II - GUC - Dr. Ayman Alserafi 35

ICA II - GUC - Dr. Ayman Alserafi 36

ICA II - GUC - Dr. Ayman Alserafi 37

ICA II - GUC - Dr. Ayman Alserafi 38

Make sure contractual

ICA II - GUC - Dr. Ayman Alserafi 39

ICA II - GUC - Dr. Ayman Alserafi 40

 One opportunity is to improve architectures and operating systems to

Make sure cloud service

ICA II - GUC - Dr. Ayman Alserafi 43

Cloud service provider should provide a