Cloud1 Computing 01

1. Cloud Computing 101
BY HEARTIN KANIKATHOTTU

2. Introduction to cloud
computing

3. History of
computing
 Bare metal
 A single host machine
 Server Virtualization
 One host machine with
multiple virtual machines
managed by hypervisors.
 Containers
 Multiple light weight
containers in one host
machine or one virtual
machine.

4. Introduction to
Containers
A container packages all software
components into a single deployable
unit and is often compared to a shipping
container.
Value best understood with the ‘Works
on my computer’ problem experienced
by many software developers
Containers are lightweight alternatives
to virtual machines.
Docker is one of the most popular
container product.

5. Which company
created docker?
Answer in the LIVE poll

6. Container
Orchestration
– Managing
containers
Kubernetes (K8s) is one of the most popular container
orchestration tools.
Kubernetes originally started as an internal project at
Google and later was made open source.
Kubernetes can be used for the management, scaling and
deployments of containers efficiently.
Kubernetes as a service is available on most public clouds:
EKS on AWS, GKE on Google Cloud and AKS on Azure.
Kubernetes is usually referred to as K8s.

7. Who manages the
K8s project now?
Answer in the LIVE poll

8. Road to the
cloud
 Data centers
 Abstract the actual
physical hosting
environment
 Hardware is the primary
unit of scale

9. What is cloud
computing?
 On-demand and automated
provisioning of computer
resources:
 computing, networking and
storage.
 Pay per use.
 Abstractions at different levels:
 Infrastructure
 Platform
 Software
 Containers
 Functions
 Backend

10. Advantages of cloud computing
Replaces up-front capital infrastructure expenses (CapEx) with low variable operational costs
(OpEx) that scale with your business.
1.Provides flexibility between capital expenditure (CapEx) and operational expenditure
(OpEx).
Businesses no longer need to plan for and procure IT infrastructure weeks or months in
advance.
Benefit from the experience and purchasing power of a cloud provider such as AWS,
Azure, GCP etc.

11. Advantages of cloud computing (Cont.)
Do not have to worry about hardware maintenance.
1.Do not have to worry about securing physical servers
Flexibility to save long term using reserved VMs (CapEx).
Can close on-premise data centers once we migrate to public cloud.

12. Question
 Which expenditure model should you use
for migrating all the virtual machines to an
Azure pay-as-you-go subscription?
 operational
 elastic
 capital
 scalable

13. Features of cloud computing
 High Availability - Ensuring an agreed level of operational performance, usually uptime.
 Scalability - Capability to adapt and perform well under an increased or expanding workload or
scope. Also referred to as Dynamic scalability.
 Elasticity – Allocation of required resources to meet current needs. Scalability is generally achieved
through elasticity
 Fault Tolerance - Ensuring that servers or services remain available even if some fail.
 Disaster Recovery - Maintain or quickly resume mission-critical functions after a failure.
 Low latency – Ability to access services faster through internet. May use CDNs.

14. Achieving BCDR through Azure Site
Recovery
 Azure site recovery help us achieve business continuity and disaster recovery (BCDR) strategy
 It helps us keep our data safe, and our apps and workloads online, during planned and unplanned
outages.
 Azure Recovery Services contributes to your BCDR strategy:
 Site Recovery service replicates workloads running on physical and VMs from a primary site to a
secondary location. When an outage occurs at primary site, we fail over to secondary location. After the
primary location is running again, you can fail back to it.
 Backup service: The Azure Backup service keeps your data safe and recoverable.

15. Exam Tips
 Capital expenditure (CapEx) is the initial investments such as buying fixed assets. Operational
expenditure (OpEx) is the ongoing costs including annual costs.
 With on-premise, these features means more hardware that will be used only when needed, but
with cloud these resources are provisioned on-demand.
 In High availability, performance and uptime in response to increasing demand is considered. With
Fault tolerance, only uptime in response to a failure is considered.
 In Fault tolerance, service continues after failure. In Disaster recovery, service may be interrupted
but recover faster.
 Scale up means replacing servers with more capacity ones (or increasing its capacity). Scale out
means adding more servers and processing in parallel.

16. Traditional
abstractions
for cloud –
IaaS, PaaS
and SaaS
• abstract the physical infrastructure layer and expose computing, storage and
networking as service.
• Unit of scale is the operating system.
• Examples of IaaS include Azure Virtual Machine.
Infrastructure as a Service (IaaS)
• Cloud provider takes care of the virtual machine and operating system and
developer is only responsible for the application.
• With PaaS, application is the unit of scale.
• Examples include Azure SQL Database.
Platform as a Service (PaaS)
• Software that is available on cloud as a service.
• Unit of scale is software.
• SaaS services include email, video streaming services, document sharing
services etc.
Software as a Service (SaaS)

17. Traditional cloud abstractions - Responsibilities
 Color code:
 Customer managed
 Cloud-provider managed

18. Question
 Recommend a cloud deployment solution
to minimize the amount of administrative
effort used to manage a web application on
cloud.
 SaaS
 PaaS
 IaaS
 Database as a Service (DaaS)

19. Question
 A company plans to deploy several custom
applications to the cloud where each
application has several prerequisite
applications and services installed. Which
cloud deployment solution is suitable for all
the applications.
 SaaS
 PaaS
 IaaS

20. Exam Tips
 An IaaS solution provide control of the operating systems that host applications.
 A PaaS solution provides the ability to scale the platform automatically
 In a SaaS solution, end users are responsible for only configuring the SaaS
solution.

21. Multi-cloud PaaS
 Support multiple cloud providers.
 Examples: Cloud Foundry, Heroku.
 Cloud Foundry
 Multi-cloud application platform as a service governed by the Cloud Foundry
Foundation.
 Heroku
 Cloud platform as a service supporting several programming languages.
 It now supports Java, Node.js, Scala, Clojure, Python, PHP, and Go.

22. Serverless Computing
 We pay only for the time we execute our code.
 Originally the term serverless was used to refer to Function as a Service (FaaS).
 FaaS allows us to run code (functions) without worrying about managing the server and
the runtime environment.
 Currently also be used to refer to Backend as a Service (BaaS) and other fully
managed applications, where we can create backends or services without
provisioning or configuring any database servers.
 Serverless computing is made possible mostly using containers.
 Examples: AWS Lambda functions, Azure functions.

23. Type of clouds – Cloud deployment models
Public cloud Private cloud Hybrid cloud

24. Question
 An organization that hosts its infrastructure
in a __________ can close its data center.
 private cloud
 hybrid cloud
 public cloud

25. Question
 Recommend a solution that provides
additional resources to your on-premises
network with minimizing capital and
operational expenditure costs.
 a complete migration to the public
cloud
 an additional data center
 a private cloud
 a hybrid cloud

26. Tips
 Important characteristics of public cloud include metered pricing and self-service
management (automations)
 The public cloud is shared by multiple corporations each using a portion of the
resources in the cloud
 A private cloud may not be disconnected from internet, but the access may be
limited to people within an organization or whomever they designate

27. Popular public cloud providers
Amazon Web
Services (AWS)
Azure
Google Cloud
Platform (GCP)
IBM Cloud Oracle Cloud Alibaba Cloud

28. Are cloud-native
applications specific to
cloud providers?
Answer in the LIVE poll

29. What is cloud Native?
 A cloud-native application is an application that has been designed and implemented to run on
cloud and to embrace horizontal elastic scaling.
 The word “native” in “cloud native” may make us thing that only the applications developed
natively within a cloud can be considered cloud native. This is not true. The “cloud native” phrase
is used commonly throughout most IT circles today. Other phrases like “cloud friendly,” “cloud
ready,” or “cloud optimized” could be used for the same, but they are neither as catchy nor as
widely recognized as the term “cloud native”.