Cloud Computing

sadiakhan4422@gmail.com
 Advantages and Disadvantages
of Cloud Computing
 Advantages together with Resource sharing, Elasticity,
Resource Aggregation, User convenience
 Lower Computer Costs

 Improved Performance

 Reduced Software Costs

 Instant Software Updates

 Improved Document Format Compatibility

 Unlimited Storage Capacity

 Increased Data Reliability

 Universal Information Access

 Latest Version Availability

 Easier Group Collaboration

 Device Independent
 Advantages and Disadvantages
of Cloud Computing
 Disadvantages
 Required constant internet connection
 Does not work well with low-speed connection
 Features might be limited
 Can be slow
 Stored data might not be secured
 Stored data can be lost
 General Concerns: vendors or CSP dependency
 Why cloud computing could be
successful when other paradigms
have failed?
 It is in a better position to exploit recent advances in
software, networking, storage, and processor technologies
promoted by the same companies who provide cloud
services.
 It is focused on enterprise computing; its adoption by
industrial organizations, financial institutions, government,
and so on could have a huge impact on the economy.
 A cloud consists of a homogeneous set of hardware and
software resources.
 The resources are in a single administrative domain (AD).
Security, resource management, fault-tolerance, and quality
of service are less challenging than in a heterogeneous
environment with resources in multiple ADs.
Relevant Technologies
 Major building blocks of
Cloud Computing Architecture
Cloud Computing Architecture
vs. “XaaS”
XaaS Stack Views: Customer View
vs. Provider View
 Architecture for Elasticity
…elasticity and cost requirements impact architecture
It has two broader approaches
Service Models (XaaS)
 Service Models (XaaS)
Broad network access (Cloud) + Resource pooling (Cloud)
+ business-driven infrastructure On-demand (SOI)
+ service-oriented (SOI)=XaaS

XaaS fulfills all four demands!

Service Models (XaaS)
 Requirements of CSP
What are the things/aspects CSP looking for:
 Classical Service Model
 Like OSI Model
 Logical representation

 of Components

 Communication, Storage and

Servers are basic block over which

it works.
 need virtualization of three blocks
 These are essential components

Which makes this IaaS as feasible

Classical Service Model
 Key Impact of Cloud Computing For IT Function:
From Legacy IT to Evergreen IT
In legacy IT, all components are tightly coupled.
In Evergreen IT, all components are not tightly coupled/flexible. It provide
better utilization of resources, better return on investment etc
 Client Sever Architecture
Important Architecture but not flexible, with its own advantages and
disadvantages, we are migrating to Service-Oriented-Architecture(SOA)
which is flexible with heterogeneous things
Client Sever Model
vs. Cloud Model
Cloud Service Model
 SaaS Characteristics
 Web access to commercial software.
 Software is managed from a central
location(logically central).
 Software delivered in a “one to many” model.
 Users not required to handle software upgrades
and patches.
 Application Programming Interfaces (APIs) allow
for integration between different pieces of
software.
 Applications where SaaS
may be useful
 Applications where there is significant interaction
between the organization and the outside world. e.g.
email newsletter campaign software.
 Applications that have need for web or mobile
access. e.g. mobile sales management software.
 Software that is only to be used for a short term
needs. e.g. collaboration software for a specific
project. Exam software etc
 Software where demand spikes significantly for
particular time window, e.g. tax or billing software
used once a month.
 Applications where SaaS
may be useful
 SaaS is widely accepted to have been introduced
to the business world by the Salesforce product ;
Customer Relationship Management (CRM).

 CRM is the most popular SaaS application area,

 however e-mail, financial management, customer

service and expense management have also
gotten good uptake via SaaS.
 Applications where SaaS
may not be the best option
 Applications where extremely fast processing of
real time data is required. Where HPC required like
in disaster management

 Applications where legislation or other regulation

does not permit data being hosted externally. Like
in university email server

 Applications where an existing on-premise solution

fulfills all of the organization’s needs.
 PaaS Characteristics
 Services to develop, test, deploy, host and maintain
applications in the same integrated development environment.
 Web based user interface creation tools help to create,
modify, test and deploy different UI scenarios.
 Multi-tenant architecture where multiple concurrent users
utilize the same development application.
 Built in scalability of deployed software including load
balancing and failover.
 Integration with web services and databases via common
standards.
 Support for development team collaboration – some PaaS
solutions include project planning and communication tools.
 Tools to handle billing and subscription management.
 Scenarios where PaaS is
useful
 PaaS is especially useful in any situation where multiple
developers will be working on a development project or where
other external parties need to interact with the development
process.
 PaaS is useful where developers wish to automate testing
and deployment services.
 The popularity of agile software development, a group of
software development methodologies based on iterative and
incremental development, will also increase the uptake of
PaaS as it eases the difficulties around rapid development
and iteration of software.
 Some examples of PaaS include Google App Engine,
Microsoft Azure Services, and the Force.com platform.
 Scenarios where PaaS is
not ideal
 Where the application needs to be highly portable in terms of
where it is hosted.

 Where proprietary languages or approaches would impact on

the development process. Mission critical etc not required
open source or public things.

 Where a proprietary language would hinder later moves to

another provider – concerns are raised about vendor lock-in

 Where application performance requires customization of the

underlying hardware and software.
 Characteristics of IaaS
 Resources are distributed as a service

 Allows for dynamic scaling

 Has a variable cost, utility pricing model

 Generally includes multiple users on a single piece

of hardware
 Scenarios where IaaS
make sense
 Where demand is very volatile – any time there are significant
spikes and troughs in terms of demand on the infrastructure

 For new organizations without the assets to invest in hardware

 Where the organization is growing rapidly and scaling

hardware would be problematic

 Where there is pressure on the organization to limit assets

expenditure and to move to operating expenditure

 For specific line of business, trial or temporary infrastructural

needs
 Scenarios where IaaS
may not be the best option

 Where regulatory compliance makes the offshoring or

outsourcing of data storage and processing difficult

 Where the highest levels of performance are required, and on-

premise or dedicated hosted infrastructure has the capacity to
meet the organization’s needs
 SaaS
providers
 PaaS
providers
 IaaS
providers
 XaaS
different stacks