Module 1

Introduction to Cloud Computing

By,
Krishna Sowjanya K,
Dept. of CSE, DSU
Cloud????
Scenario 1:
• Suppose you want to host a website. What do you need?

More Traffic ? Upgrade Servers

Buy Servers

Maintain and Monitor the Servers

Problems in Scenario 1
• If you consider cost, it is expensive for the setup.

• Monitoring and Maintaining servers is tedious,

as it requires extra personnel.

• Servers will be idle as traffic is not constant.

Scenario 2:
• Data generation is more. How to handle this data?
CLOUD
• “The Cloud” refers to the servers, software, databases that are
accessed over the internet.
• These servers are located in data centers all over the world.

• According to Wikipedia, “Cloud Computing” is the on-demand

availability of computer system resources.
• Resources can be Storage, Computing power, Network, Software etc.
Cloud Computing
• According to NIST, “Cloud Computing” is defined as follows:

• “Cloud computing” is a model for enabling ubiquitous, convenient, on-

demand network access to a shared pool of configurable computing resources
(e.g., networks, servers, storage, applications, and services) that can be
rapidly provisioned and released with minimal management effort or service
provider interaction.

NIST - NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY

Cloud Computing
• “Cloud computing” is the delivery of on-demand computing services
from applications to storage and processing power over the internet
and on a pay-as-you-go basis.

• A dynamically scalable system that provides internet-based services

often virtually.
Data Centers
• A “Data center” is a facility composed of networked computers and
storage that the organizations use to process, store large amounts of
data.

• A Data center must also contain an adequate infrastructure such as

power distribution and supplemental power subsystems.

• Electrical switching, uninterruptable power supplies, backup

generators, ventilation, data center cooling systems.
Data Center

https://www.youtube.com/watch?v=43mcD274Sqs

https://www.youtube.com/watch?v=80aK2_iwMOs
Quick revision of problems in Scenario 1 &
2
• Cost

• Upgradation / scalability

• Less memory space

Cloud Benefits
• Cost efficient: Saves the cost of purchasing, maintaining, upgrading
the systems.

• Storage space: Provides unlimited space for storage.

• Scalability: The resources can be scaled up/down based on the usage.

Additional Benefits
• 24 X 7 Availability
• Automated updates on software
• Security
• Reliability
• Pay- as –you-use model
• Disaster Recovery
• Quality control (SLAs)

SLA – SERVICE LEVEL AGREEMENTS

Stakeholders of Cloud
• The primary stakeholders of cloud according to NIST are as follows:

• Cloud Provider
• Cloud Carrier
• Cloud Broker
• Cloud Auditor
• Cloud Consumer
Stakeholders of Cloud contd..
• Cloud Service Providers: A person/Organization that delivers cloud
services to end-users.

• Cloud Carrier: The Mediator who offers connectivity that allow access
to the services.

• Cloud Broker: An organization that manages the performance, user,

and delivery of cloud services
Stakeholders of Cloud contd…
• Cloud Auditor: An entity that can conduct assessment of cloud
services, security, performance etc. These are provided by Cloud
Service Providers (CSP)

• Cloud Consumer: A cloud consumer is the end-user who utilizes the

services provided by the CSP.
Cloud Service Providers (CSP)
Cloud Carriers
Cloud Service Models
• Cloud computing is offered in three different service models.
Each model provides a unique set of business requirements.

• Infrastructure as a service (IaaS)

• Platform as a service (PaaS)
• Software as a service (SaaS)
Scenario 1:
• Suppose you want to travel somewhere
Scenario 1 Explained
• On-Premise (Owning) : Responsible for its maintenance, and
Upgrading.
• IaaS (Leasing) : The maintenance, and upgradation is done
by the owner.
• Paas (Using the service): Use the services.
• Saas (Sharing) : Service will be shared among different users.
Scenario 2
Services in Cloud
Service Models
Infrastructure-as-a-Service (IaaS)
• IaaS is a way to deliver the cloud computing infrastructure like Server,
storage, network .
• The users can access these resources over internet as an on-demand
service.
• The charges are applied based on pay-you-go-basis.
• Examples: Amazon, Rackspace, EC2, Nimbus
IaaS Pros & Cons:
• Pros:
• Cost-effective due to pay-as-you-go basis.
• Easy to use due to automated deployment of hardware.

• Cons:
• Vendor outages make customers unable to access their
data for a while.
• The need for team training to learn how to manage.
When to Use IaaS:
• If you are a small company or a startup that has no budget for
creating your own infrastructure
• If you are a rapidly growing company and your demands are
unstable and changeable
• If you are a large company that wants to have effective
control over infrastructure but pay only for the resources you
actually use
Platform-as-a-service (PaaS)
• PaaS delivers a framework for developers that they can build upon
and use to create customized applications.
• Provides a platform for software creation.
• All the servers, storage and networking can be managed by the
enterprise.
• Ex: Google App Engine, Heroku
PaaS Pros & Cons
• Pros:
• Development process is quickened and simplified.
• Reduced expenses
• Automated company policy
• Cons:
• Compatibility of existing infrastructure
• Dependency on vendor’s speed, reliability and support
When to use PaaS
• Multiple developers work on one project
• You want to create your own customized apps
Software as a Service (SaaS)
• SaaS utilizes the internet to deliver applications to the users.
• Majority of SaaS applications run directly through the web
browser.
• They do not require any downloads or installations on the
client side.
• Examples: Gsuite, Cisco WebEx, Dropbox
SaaS Pros & Cons:
• Pros:
• Accessible from anywhere
• Cost effective
• Easy to scale
• Excellent for collaborative working
• Cons:
• Portability issue
• Depends on the internet
• Loss of control and customization
When to use SaaS:

• If a company needs to launch a ready-made

software quickly.
• If an app is required for temporary basis
Deployment Models
• A cloud deployment model is defined according to where the
infrastructure for the deployment resides and who has
control over that infrastructure.

• Each cloud deployment model satisfies different

organizational needs, so its important to choose a model that
will satisfy the needs of the organization.
Deployment Models
Private Cloud
• Consider the organizations, Defense and Banks.
• The data they maintain is HIGHLY SENSITIVE.
• There is a need for greater control over the data in
these type of organizations.
• Solution: Private Cloud
Private Cloud
• NIST defines “Private Cloud” as the cloud
infrastructure that is provisioned for exclusive use by a
single organization with multiple customers.
• It may be owned, managed and operated by the
organization.
• It may be On-Premise or Hosted externally.
Private Cloud
Private Cloud Pros & cons
• Pros:
• Data Privacy
• Security
• Supports Legacy systems (cannot access the public cloud)
• Cons:
• Higher Cost
• High maintenance
Public Cloud
• Consider an organization with growing and fluctuating
demands.
• Security in not a primary concern.
• Needs Computational Power
• Ex: E-commerce websites
• Solution: Public Cloud
Public Cloud
• NIST defines the “Public Cloud” as the cloud
infrastructure that is provisioned for the open use by
the general public.
• It may be owned, managed, operated by a business,
academic or government organization.
• It exists on the premise of the cloud provider.
• Gsuite, Salesforce
Public Pros & Cons:
• Pros:
• Minimal Investment
• No Hardware setup
• No infrastructure Management
• Cons:
• Data Security and Privacy Concerns
• Reliability issues
• Service/License Limitation.
Community Cloud
• NIST defines “Community Cloud” as a cloud infrastructure that is
provisioned exclusively for specific community that have shared
concerns. (Security, Requirements, Policy )
• It may be owned, managed and operated by one or more of the
organizations in the community.
• It may exist on or off premise.
Community Cloud Pros & Cons:
• Pros:
• Smaller Investment
• Setup Benefits
• Cons:
• Shared resources
• Not as popular as private and public
Hybrid Cloud
• Consider an organization that has critical data, it
prefers private cloud.
• It has limited infrastructure.
• In the case of scalability, a private cloud cannot be
configured.
• Solution: Hybrid Cloud (Cloud Bursting)
• Burst or expand into public cloud
Hybrid Cloud
• NIST defines “Hybrid Cloud”, as the cloud infrastructure,
which is a combination of two or more deployment models.
• In hybrid cloud, each model is unique.
• Less sensitive data can be stored on public cloud
• An organization runs applications on-premises, but due to
heavy load, they can burst into the public cloud.
Hybrid Cloud Pros & Cons:
• Pros:
• Cost effectiveness
• Flexibility
• Security
• Cons:
• Complexity
• Specific Use case to separate critical and sensitive data
Comparison of Cloud Deployment Models
Deployment Model
--------------------------
Public Cloud Private Cloud Hybrid Cloud Community
Attribute Cloud
Ownership Customers Single Organization Service Provider and Two or more
Consumer Organizations
Performance Low to Medium High Moderate High

Setup Cost Low High Medium Depends on no. of

Organizations
Used by Anyone Limited people Medium Depends on no. of
accessibility Organizations
Security Low Highest Medium High
Comparison of Cloud Deployment Models
Deployment Model
--------------------------
Public Cloud Private Cloud Hybrid Cloud Community
Attribute Cloud
Maintenance Cost Low Highest Moderate High

Cloud Bursting Not supported Not Supported Supported Not Supported

User’s Control Limited Control Full Control Full over private High control but
over infrastructure cloud and Limited limited by
on public cloud community policies
Workload Suitable for Normal Not suitable for High Highly dynamic or Suitable for handling
workloads workloads changeable large workloads
Benefits of Cloud Computing
• Profitable:
• Highly cost-efficient because of the process of pay-as-you-use, pay-
as-you-go, pay-as-you-demand.
• Highly scalable
• Cloud can easily upgrade or downgrade the requirements
• Easily accessible:
• Cloud can be accessed from anywhere remotely provided internet.
And also with many devices like smartphone, table, Laptop.
Benefits of Cloud Computing
• Security:
• Uses encryption algorithms to secure the data and also does not
allows any illegitimate access.
• Productivity:
• No downtime (caused due to version upgrades, security patches)
• Availability: (up-time)
• Maintains 99.9% availability making servers and other services
available for use around the clock.
Benefits of Cloud Computing
• Access to the Latest software
• Without investing time in software upgrades, the latest
version of a software can be used.
• Speed:
• The time taken to provide the services is very less when
compared to the traditional methods.
Risks:
• Less Visibility and Lack of control:
• When transitioning to cloud, some visibility and control over the
assets will be lost because of policies and infrastructure.
• Internet APIs can be compromised:
• APIs will have some vulnerabilities, exposing them to potential
threats.
• Vendor Lock-in:
• Situation where the cost of switching to a different vendor is so
high that the customer is essentially stuck with the original vendor
Risks:
• Increased complexity strains IT Staff
• Insider attack
• Trust & Security
Challenges
• Cloud Spend
• Cost
Challenges:
• Lack of expertise
Challenges:
• Multi-cloud
Challenges:
• Security
• Privacy
• Confidentiality
Challenges:
• Compliance: Laws and regulations that apply to use the cloud.
Cloud Migration
• Re-designing the architecture of cloud.
• Training users on new systems
• Bandwidth cost Organization to Cloud Migration
• Migration expenses.

Cloud to Cloud Migration

Vendor Lock-in
• Vendor lock-in refers to a situation where the cost of switching to a
different vendor is so high that the customer is essentially stuck with
the original vendor. 
Cloud Architecture
Front end
• Used by client.
• Contains client side interfaces.
• Ex: Chrome, Firefox, IE.
• Devices: Mobile, Laptop, Desktop, Tablets
Client Infrastructure
• Client Infrastructure is a Front end component. It provides
GUI (Graphical User Interface)  to interact with the cloud.
Back end
• Used by service provider.
• Manages all the resources required to provide the
services.
• Includes data storage, security, VMs, deployment
models etc.
Cloud Components
• Application:
• Any Software or Platform that a client wants to access
• Service:
• Cloud computing offers three servicing models (IaaS, PaaS, SaaS)
• Runtime Cloud:
• Provides the execution and runtime environment.
Cloud Components
• Storage:
• Provides huge amount of space to store and manage the data.
• Infrastructure:
• Servers, Storage, Network devices.
• Management:
• Manages all the components and establishes coordination
between them.
Cloud Components
• Security:
• It is a built-in back end component
• Internet:
• Medium through which front end and back end can interact and
communicate with each other.
Virtualization
• Virtualization is a technology that allows you to create multiple
environments or resources from a single, physical hardware system.
• The ability to emulate
hardware via software.
Types of Virtualization
• Desktop Virtualization
• Network Virtualization
• Storage virtualization
• Data virtualization
• Application virtualization
• Data center virtualization
• CPU virtualization
• Linux Virtualization
Introduction to Google App Engine
• Google App Engine is a Platform-as-a-Service (PaaS) Product.
• Provides a platform to host web applications.
• It provides scalability.
• Often called as GAE or App Engine.
Languages supported by GAE
Features
• Popular languages
• Open and flexible
• Fully managed
• Powerful application diagnostics
• Application versioning
• Traffic splitting
• Application security
• Services ecosystem
Benefits of GAE
• Open and familiar languages and tools
• Pay only for what you use
• Just add code
• Secure Framework
• Platform Independence
• Quality Services and APIs
Companies using GAE
THANK YOU