Cloud
Computing
Presented By:
Dr. Srikanta Pradhan
Assistant Professor Department
of Data Science and Engineering
Manipal University Jaipur,
Jaipur
Introduction to Cloud Computing
Virtualization and Infrastructure as
a service Hyper Converged
Infrastructure
Introduction to Cloud
Computing
Edge vs Fog vs Cloud
What is
Cloud
Computing
It is a techno-business
?
disruptive model of using
distributed large-scale data
centers either private or public
or hybrid offering customers a
scalable virtualized
infrastructure or an abstracted
set of services qualified by
service-level agreements
(SLAs) and charged only by the
abstracted IT resources
consumed.
What
comprises
Cloud
Computing?
• NIST Visual Model of
Cloud Computing
Essential
Characteris
tics
What
comprises
Cloud
Computing?
• NIST Visual Model of
Cloud Computing
• Service Models are the
Servi Reference Models on which
the Cloud Computing is Based.
ce
Model
s
Products
at each
Service
Level
Cloud
Infrastruct
ure
• Infrastructure
• Platform
• Application
Infrastructur
e as a
Service
(IaaS)
On
premise
Data
Centers
• Key Challenges
• Capital expenditure to purchase physical
and digital assets
• Building
• People
• Expansion
Given the current state of extreme weather events
impacting all areas of the globe – a single on-premise
data center can appear quite vulnerable; something may
occur nearby that server’s power, floods the grounds, or
limits access to the facility.
• With Infrastructure as
a Service – Data
Center manages the
Iaa physical
S infrastructure
required to run a
proper data
center.
Iaa
• With Data Center owning responsibility for the physical infrastructure – in an
S infrastructure as a service model – the business manages everything else.
• A good conceptual model of this would be using Azure to spin up virtual machines
upon which the business installs and maintains all of the necessary software and tools
(i.e. SQL Server, Windows, etc)
• Here the business still retains responsibility for upgrading software, installing patches,
etc. They are essentially renting space from which to do this.
• What you gain: Computer/Server
• Consumer: SysAdmins
• Examples: [Link], Go Grid, Amazon Web Services (AWS)
• The advantages of IaaS versus On-
premise
•Pay for what you use •Better ability to scale and grow IT workloads
•Improved stability and reliability •Reduction of capital expenditures
•Better disaster recovery •Future proof
•Better security •Free up IT staff
Paa
S
• Platform as a Service is the next natural iteration of
computing
cloud
• In this model, Data Centre manages all the
.infrastructure, as well the software tools to connect to
infrastructure. The business manages tools they wish to
physical
within
that that framework, but is not responsible for
upgrades
use to the
software
• So in the chart above – the business brings the data and
tool.
to provision the desired data application, but is not
for patching the SQL Server running the database or
pays
responsible
it when a new version is released. This is all handled by
upgrading
Centre.
Data
• What you gain: Application/Framework
• Consumer: App Developers
• Examples: [Link], Google App Engine, Microsoft Azure
Advantages of PaaS
• Affordable access to sophisticated tools
• Faster development
• Easy management of application lifecycle
Software as a
Service (SaaS)
• Software as a Service is Data Centre providing a
complete
software package end to end.
• They manage everything.
• Some great examples here would be Teams,
OneDrive, Outlook, and Skype.
• We just interact with these tools, and have
•little control
What inBusiness Functionality
you gain:
how they are designed, deployed, or managed.
• Consumer: End Users
• Examples: Google Docs/Gmail, FreshBooks, Salesforce, BaseCamp
Anything
as a
Service
• This only makes sense as the idea is to
(XaaS)
leverage nearly any technology product –
as a service.
• This section could be extensive – but let’s
try to lay a foundation for what the future
will bring as the movement of physical
hardware to the cloud continues.
• Desktop as a Service
• IoT as a Service
What
comprises
Cloud
Computing?
• NIST Visual Model of
Cloud Computing
Cloud
Deployment
Models
• Public: Infrastructure made available to general public or large industry
group; owned by the organization selling the service
• Private: Infrastructure operated solely for a single organization; may be
managed by the organization or a third party; may be located on-
premise or off-premise
• Community Cloud: Infrastructure is shared by several organizations and
supports a specific community that has shared concerns (e.g. mission,
security requirements, policy, compliance etc.); may be managed by the
organization or a third party; may be located on-premise or off-premise
• Hybrid/ Multi-Cloud: Infrastructure is a composition of two or more
clouds; remain unique entities but bound together by standardized or
proprietary technology that enable data and application portability
Cloud Deployment Models
Why adopt Cloud Computing?
• Scalability
• Organizations have access to many resources that scale based on user demand.
• Elasticity
• Organizations can request, use, and release as many resources as needed based on
changing needs
• Virtualization
• Each user has a single view of the available resources, independently of how they are
arranged in terms of physical devices
• Lower Infrastructure Cost
• The pay-per-use model allows an organization to only pay for the resources they
need with basically no investment in the physical resources available in the cloud.
There are no infrastructure maintenance or upgrade costs
Why adopt Cloud Computing?
• Availability
• Organizations have the ability for the user to access data and applications from
around the globe
• Collaboration
• Organizations are starting to see the cloud as a way to work simultaneously on
common data and information
• Risk Reduction
• Organizations can use the cloud to test ideas and concepts before making major
investments in technology
• Reliability
• In order to support SLAs, cloud providers have reliability mechanisms that are much
more robust than those that could be cost-effectively provided by a single
organization
Barriers to Cloud Adoption
• Security – organizations do not have control of or know where their data is
being stored
• Interoperability – universal set of standards and/or interfaces has not yet
been defined, resulting in a significant risk of vendor lock-in
• Resource Control – amount of control that the organization has over the
cloud environment varies greatly
• Latency - all access done via internet, latency into every communication
between the user and the environment
• Platform or Language Constraints – support for specific platforms and
languages only
• Legal Issues – concerns over jurisdiction, data protection, fair information
practices, and international data transfer