Module 1: Understanding Cloud Computing

Cloud origins and influences

INTRODUCTION
Cloud computing:
 Cloud computing is the on-demand delivery of IT resources over the Internet with
pay-as-you-go pricing. Instead of buying, owning, and maintaining physical data
centers and servers, we can access technology services, such as computing power,
storage, and databases, on an as-needed basis from a cloud provider like Amazon
Web Services (AWS).
Services include:
 Storage
 Database Servers
 Networking
 Software
 Analytics Intelligence
Key benefits:
 Faster innovation
 Flexible resources
 Economies of scale
EARLY CONCEPTS AND PRECURSORS
Mainframe and Time-sharing (1950s-1960s).
 Large, powerful computers are primarily used by businesses and government
organizations.
 Capabilities: Capable of handling and processing vast amounts of data.
 Usage: Centralized computing; multiple users connected via terminals.
 Cost: Expensive and required a significant investment in infrastructure.
Time-Sharing:
Concept: Multiple users accessing a single mainframe computer simultaneously.
Technology: Use of terminals connected to the mainframe.
Efficiency: Improved resource utilization by sharing computing power among
many users.
Innovation: Allowed multiple users to interact with a computer at the same time,
paving the way for the development of modern multi-user systems.
Impact: Laid the groundwork for later developments in distributed computing
and cloud computing by demonstrating the feasibility of resource sharing.
Significance:
Resource Sharing: Demonstrated the benefits and efficiency of sharing
computing resources.
User Experience: Enhanced user experience by allowing multiple users to run
applications concurrently.
• Distributed computing involves using
multiple computers, or nodes,
connected over a network to solve a
problem or perform a task as if they
were a single system.
• Instead of relying on a single,
powerful machine, the workload is
spread across the network, allowing
for increased processing power,
scalability, and resilience.
ARPANET (1960s-1970s).
ARPANET: Advanced Research Projects Agency Network. Initiated by: U.S.
Department of Defense's ARPA (Advanced Research Projects Agency).
UCLA (University of California, Los Angeles) and ARPANET
Impact on Cloud Computing:
Networking Foundation: ARPANET's success showcased the viability of
large-scale, distributed networks, fundamental to cloud computing.
Ongoing Influence: Packet switching and network protocols developed
during ARPANET's early days continue to underpin cloud infrastructure
today.
Development of the Internet
Evolution of the Internet (1980s-1990s) &Growth of networking and TCP/IP
protocol.
• 1980’s TCP/IP Protocol
• 1983, foundational protocol for the internet
• 1984, DNS (like www.example.com) into IP addresses,
Email and Newsgroups :
Communication, forum for discussions on various topics
1990s: World Wide Web Commercialization
HTTP (Hypertext Transfer Protocol) and HTML (Hypertext Markup
Language) enabled the creation and linking of web pages
Development of the Internet
Web browsers:
Mosaic graphical web browser for non technical users), released in 1993
Netscape Navigator (popularized web browsing), launched in 1994
Commercialization:
Search Engines:
Early search engines like Archie, Gopher, and later, Yahoo! (1994) and Google
(1998), helped users find information on the growing web.
E-commerce:
Introduction of online shopping
Virtualization Technology
Introduction of Virtual Machines (VMs) & Impact of Virtualization.
• VMs are software-based emulations of physical computers, allowing multiple
VMs to run on a single physical machine
• VMs replicate the architecture of a real computer, including CPU, memory,
storage, and networking. Allows multiple operating systems to run on a single
hardware platform, isolated from each other.
• Virtualization is a cornerstone of cloud computing, enabling multi-tenancy and
resource pooling.
• Increased Efficiency, Cost Savings, Dynamic Allocation, and Scalability.
Grid Computing
Concept and Development, Projects and Examples.
Grid computing is a distributed computing model that involves a network of
loosely coupled computers working together to perform tasks, often
involving complex computations or large datasets.
Characteristics:
Distributed Resources, Parallel Processing, Resource Sharing, Scalability,
Heterogeneity, Virtual Organizations
via grid technologies.
Scientific Research Projects:
SETI@home: in 1999. Volunteers use spare processing power on their
personal computers to analyze radio signals
Environmental and Climate Research:
Earth System Grid: studying global climate change.
Birth of Cloud Computing
Early Cloud Services, Key Milestones.
Cloud computing evolved from the development and convergence of internet services
and distributed computing technologies.
1960s: IBM's mainframes offering time-sharing services.
1990s:Salesforce.com (1999): delivering applications over the internet.
2002:Amazon Web Services -Public.
2006: Google Cloud Platform (GCP) launched, including Google App Engine for web
applications.
2008:Microsoft Azure ,
2009: VMware ,
2010:OpenStack: An open-source cloud computing platform,
2014:Docker popularized containerization, improving cloud computing efficiency.
2019:Kubernetes: Open-sourced by Google, became the standard for container
orchestration in the cloud.
Influences on Cloud Computing
Technological Advances.
Virtualization, Broadband Internet, Distributed Computing, Containerization
Economic Factors.
Cost Reduction, Pay-as-You-Go Pricing, Resource Optimization
Business Needs.
Scalability,
Disaster Recovery and Business Continuity,
Remote Work Enablement,
Collaboration
Impact of Cloud Computing
On Businesses:
Innovation, scalability, reduced IT overhead.
On Individuals: Accessibility, collaboration, remote work capabilities.
Challenges and Considerations
Security and Privacy:
Data breaches (unauthorized access to confidential information), compliance.
Reliability and Downtime:
Service outages, dependency on providers.
Future of Cloud Computing
Emerging Trends:
Edge computing, AI integration, multi-cloud strategies.
Basic Concepts and Terminology

Cloud
A cloud refers to a distinct IT environment that is designed for the purpose of
remotely
provisioning scalable and measured IT resources. The term originated as a
metaphor
for the Internet, which is, in essence, a network of networks providing remote access
to a set of decentralized IT resources. This same symbol is now used to specifically
represent the boundary of a cloud environment, as shown in Figure 3.1.
 As a specific environment used to remotely provision IT resources, a cloud has a
finite boundary. There are many individual clouds that are accessible via the
Internet.
 The Internet provides open access to many Web-based IT resources, and a cloud
is typically privately owned and offers access to IT resources that are metered.
 Much of the Internet is dedicated to the access of content-based IT resources
published via the World Wide Web.
 IT resources provided by cloud environments, on the other hand, are dedicated to
supplying back-end processing capabilities and user-based access to these
capabilities. Another key distinction is that it is not necessary for clouds to be Web-
based, even if they are commonly based on Internet protocols and technologies.
 Protocols refer to standards and methods that allow computers to communicate
 with each other in a pre-defined and structured manner.
 A cloud can be based on the use of any protocols that allow for the remote access to
its IT resources.
IT Resource
An IT resource is a physical or virtual IT-related artifact that can be either software-
based, such as a virtual server or a custom software program, or hardware-based, such
as as a physical server or a network device (Figure 3.2).
On-Premise
 An IT resource that is hosted in a conventional IT enterprise within an organizational
boundary (that does not specifically represent a cloud) is considered to be located on the
premises of the IT enterprise, or on-premise for short.
 In other words, the term “on-premise” is another way of stating “on the premises of a
controlled IT environment that is not cloud-based.”
 This term is used to qualify an IT resource as an alternative to “cloud-based.”
• An on-premise IT resource can access and interact with a cloud-based IT resource.
• An on-premise IT resource can be moved to a cloud, thereby changing it to a cloud-based IT
resource.
• Redundant deployments of an IT resource can exist in both on-premise and cloudbased
environments.
Cloud Consumers and Cloud Providers
• The party that provides cloud-based IT resources is the cloud provider. The party
that uses cloud-based IT resources is the cloud consumer.
• These terms represent roles usually assumed by organizations in relation to clouds
and corresponding cloud provisioning contracts.

Scaling
Scaling, from an IT resource perspective, represents the ability of the IT resource to
handle increased or decreased usage demands.
The following are types of scaling:
• Horizontal Scaling – scaling out and scaling in
• Vertical Scaling – scaling up and scaling down
Horizontal Scaling
 The allocating or releasing of IT resources that are of the same type is referred to as
horizontal scaling.
 The horizontal allocation of resources is referred to as scaling out, and the horizontal
releasing of resources is referred to as scaling in.
 Horizontal scaling is a common form of scaling within cloud environments.
Vertical Scaling
When an existing IT resource is replaced by another with a higher or lower capacity,
vertical scaling is considered to have occurred. Specifically, the replacing of an IT
resource with another that has a higher capacity is referred to as scaling up, and the
replacing an IT resource with another that has a lower capacity is considered scaling
down. Vertical scaling is less common in cloud environments due to the downtime
required while the replacement is taking place.
Cloud Service
Although a cloud is a remotely accessible environment, not all IT resources residing
within a cloud can be made available for remote access. For example, a database or a
physical server deployed within a cloud may only be accessible by other IT resources that
are within the same cloud. A software program with a published API may be deployed
specifically to enable access by remote clients.
• A cloud service is any IT resource that is made remotely accessible via a cloud.
• Unlike other IT fields that fall under the service technology umbrella, such as
service-oriented architecture, the term “service” within the context of cloud
computing is especially broad.
• A cloud service can exist as a simple Web-based software program with a technical
interface invoked via the use of a messaging protocol, or as a remote access point for
administrative tools or larger environments and other IT resources.
Cloud Service Consumer
The cloud service consumer is a temporary runtime role assumed by a software program
when it accesses a cloud service.
As shown in Figure 3.7, common types of cloud service consumers can include software
programs and services capable of remotely accessing cloud services with published
service contracts, as well as workstations, laptops, and mobile devices running software
capable of remotely accessing other IT resources positioned as cloud services.
Goals and Benefits
Reduced Investments and Proportional Costs
Similar to a product wholesaler that purchases goods in bulk for lower price points,
public cloud providers base their business model on the mass-acquisition of IT resources
that are then made available to cloud consumers via attractively priced leasing packages.
This opens the door for organizations to gain access to powerful infrastructure without
having to purchase it themselves.
The most common economic rationale for investing in cloud-based IT resources is in the
reduction or outright elimination of up-front IT investments, namely hardware and
software purchases and ownership costs.
A cloud’s Measured Usage characteristic represents a feature-set that allows measured
operational expenditures (directly related to business performance) to replace anticipated
capital expenditures. This is also referred to as proportional costs.

Common measurable benefits to cloud consumers include:

• On-demand access to pay-as-you-go computing resources on a short-term basis (such as
processors by the hour), and the ability to release these computing resources when they are no
longer needed.
• The perception of having unlimited computing resources that are available on demand, thereby
reducing the need to prepare for provisioning.
• The ability to add or remove IT resources at a fine-grained level, such as modifying available
storage disk space by single gigabyte increments.
Increased Scalability
 By providing pools of IT resources, along with tools and technologies designed to
leverage them collectively, clouds can instantly and dynamically allocate IT resources
to cloud consumers, on demand or via the cloud consumer’s direct configuration.
 This empowers cloud consumers to scale their cloud-based IT resources to
accommodate processing fluctuations and peaks automatically or manually.
 Similarly, cloud-based IT resources can be released (automatically or manually) as
processing demands decrease.
Increased Availability and Reliability
 The availability and reliability of IT resources are directly associated with tangible
business benefits.
 Outages limit the time an IT resource can be “open for business” for its customers,
thereby limiting its usage and revenue generating potential.
 Runtime failures that are not immediately corrected can have a more significant
impact during high-volume usage periods.
 Not only is the IT resource unable to respond to customer requests, its unexpected
failure can decrease overall customer confidence.
• An IT resource with increased availability is accessible for longer periods of time
(for example, 22 hours out of a 24 hour day). Cloud providers generally offer “
resilient” IT resources for which they are able to guarantee high levels of availability.
• An IT resource with increased reliability is able to better avoid and recover from
exception conditions. The modular architecture of cloud environments provides
extensive failover support that increases reliability.
It is important that organizations carefully examine the SLAs offered by cloud
providers when considering the leasing of cloud-based services and IT resources.
Although many cloud environments are capable of offering remarkably high levels of
availability and reliability, it comes down to the guarantees made in the SLA that
typically represent their actual contractual obligations.
Cloud service provider: A CSP (cloud service provider) is a third-party company that
provides scalable computing resources that businesses can access on demand over a
network, including cloud-based compute, storage, platform, and application services.
Examples
The CSP market includes cloud providers of all shapes and sizes. The big three—Google Cloud,
Microsoft Azure, and Amazon Web Services (AWS)—are considered the established leaders.
However, there are a host of other smaller or niche players that offer cloud services as well,
including IBM, Alibaba, Oracle, Red Hat, DigitalOcean, and Rackspace.
CSPs that follow an open approach to the cloud give their customers the freedom to combine the
services and providers that best fit their needs, allowing them to move workloads to and from
on-premises and between cloud providers at any time.
Challenges of using a cloud service provider
Complex contracts: You will need to negotiate contracts and SLAs with each cloud provider you
use. Multiple providers and vendors can lead to complex SLA relationships with different
parameters and guaranteed service expectations.
Vendor lock-in: Some cloud providers do not integrate well with competitor products and
services. Becoming too dependent on a single provider can make it difficult to migrate data and
workloads to another technology stack without incurring high costs, incompatibilities, or even
legal constraints.
Security responsibility: CSPs follow a shared responsibility model, which means cloud security
is implemented by both the cloud provider and the customer. Poor understanding of a provider’s
responsibilities and your own can lead to substantial security risks or security breaches.
How to Choose a Cloud Service Provider
1.Cost
Look at usage fees and hidden charges. Include migration and talent costs.
Balance value with affordability.
Don’t focus on price alone.
2.Digital Capabilities and Processes
Evaluate ease of deployment and integration.
Support for current and future needs.
Check API standards and hybrid support.
Efficient management tools are crucial.
3.Trust
Assess the provider’s reputation and stability.
Check technical expertise and certifications.
Ensure alignment with your goals.
Support and transparency are key.
4.Open Ecosystem
Supports multi-cloud or hybrid flexibility.
No vendor lock-in with open standards.
Easily migrate apps between platforms.
Uses interoperable and open-source tech.
5.Security
Strong data protection and identity controls.
Secure physical infrastructure and policies.
Compliance with regulatory standards.
Backup, recovery, and business continuity included.
Risks and Challenges
1. Increased Security Vulnerabilities
 The moving of business data to the cloud means that the responsibility for data
security becomes shared with the cloud provider.
 The remote usage of IT resources requires an expansion of trust boundaries by the
cloud consumer to include the external cloud.
 It can be difficult to establish a security architecture that spans such a trust
boundary without introducing vulnerabilities, unless cloud consumers and cloud
providers happen to support the same security frameworks, which is unlikely with
public clouds.
 Another consequence of overlapping trust boundaries relates to the cloud
provider’s privileged access to cloud consumer data.
 The extent to which the data is secure is now limited to the security controls and
policies applied by both the cloud consumer and cloud provider.
 Furthermore, overlapping trust boundaries can occur among different cloud
consumers due to the fact that cloud-based IT resources are commonly shared.
 The overlapping of trust boundaries and the increased exposure of data can provide
malicious cloud consumers (human and automated) with greater opportunities to
attack IT resources and steal or damage business data.
 Man-in-the-Middle (MitM) attacks, Evil Twin attacks, Packet sniffing, Session
hijacking/sidejacking, Malware distribution, Identity theft and credential theft,
2. Reduced Operational Governance Control

 Cloud consumers are usually allotted a level of governance control that is lower
than that over on-premise IT resources.
 This can introduce risks associated with how the cloud provider operates its cloud,
as well as the external connections that are required for communication between the
cloud and the cloud consumer.
3. Limited Portability Between Cloud Providers
 Due to a lack of established industry standards within the cloud computing industry,
public clouds are commonly proprietary to various extents.
 For cloud consumers that have custom-built solutions with dependencies on these
proprietary environments, it can be challenging to move from one cloud provider to
another.
Multi-Regional Compliance and Legal Issues
 Third-party cloud providers will frequently establish data centers in affordable or
convenient geographical locations.
 Cloud consumers will often not be aware of the physical location of their IT resources
and data when hosted by public clouds.
 For some organizations, this can pose serious legal concerns pertaining to industry or
government regulations that specify data privacy and storage policies.
 For example, some UK laws require personal data belonging to UK citizens to be kept
within the United Kingdom.
 Another potential legal issue pertains to the accessibility and disclosure of data.
Countries have laws that require some types of data to be disclosed to certain
government agencies or to the subject of the data.
 For example, a European cloud consumer’s data that is located in the U.S. can be
more easily accessed by government agencies (due to the U.S. Patriot Act) when
compared to data located in many European Union countries
Roles and Boundaries

Cloud Provider
 The organization that provides cloud-based IT resources is the cloud provider.
 When assuming the role of cloud provider, an organization is responsible for
making cloud services available to cloud consumers, as per agreed upon SLA
guarantees.
 The cloud provider is further tasked with any required management and
administrative duties to ensure the on-going operation of the overall cloud
infrastructure.
 Cloud providers normally own the IT resources that are made available for lease by
cloud consumers; however, some cloud providers also “resell” IT resources leased
Cloud Consumer
 A cloud consumer is an organization (or a human) that has a formal contract or
arrangement with a cloud provider to use IT resources made available by the cloud
provider.
 Specifically, the cloud consumer uses a cloud service consumer to access a cloud
service.
Cloud Service Owner
The person or organization that legally owns a cloud service is called a cloud service
owner. The cloud service owner can be the cloud consumer, or the cloud provider that
owns the cloud within which the cloud service resides.
Cloud Resource Administrator
 A cloud resource administrator is the person or organization responsible for
administering a cloud-based IT resource (including cloud services).
 The cloud resource administrator can be (or belong to) the cloud consumer or
cloud provider of the cloud within which the cloud service resides.
 Alternatively, it can be (or belong to) a third-party organization contracted to
administer the cloud-based IT resource.
Additional Roles
• Cloud Auditor – A third-party (often accredited) that conducts independent
assessments of cloud environments assumes the role of the cloud auditor. The typical
responsibilities associated with this role include the evaluation of security controls,
privacy impacts, and performance. The main purpose of the cloud auditor role is to
provide an unbiased assessment (and possible endorsement) of a cloud environment to
help strengthen the trust relationship between cloud consumers and cloud providers.
• Cloud Broker – This role is assumed by a party that assumes the responsibility of
managing and negotiating the usage of cloud services between cloud consumers and
cloud providers. Mediation services provided by cloud brokers include service
intermediation, aggregation, and arbitrage.
 • Cloud Carrier – The party responsible for providing the wire-level connectivity
between cloud consumers and cloud providers assumes the role of the cloud carrier.
This role is often assumed by network and telecommunication providers.

Organizational Boundary
• An organizational boundary represents the physical perimeter that surrounds a set of
IT resources that are owned and governed by an organization.
• The organizational boundary does not represent the boundary of an actual
organization, only an organizational set of IT assets and IT resources.
• Similarly, clouds have an organizational boundary
Trust Boundary
o When an organization assumes the role of cloud consumer to access cloud-based
IT resources, it needs to extend its trust beyond the physical boundary of the
organization to include parts of the cloud environment.
o A trust boundary is a logical perimeter that typically spans beyond physical
boundaries to represent the extent to which IT resources are trusted.
o When analyzing cloud environments, the trust boundary is most frequently
associated with the trust issued by the organization acting as the cloud consumer.
Cloud Characteristics
An IT environment requires a specific set of characteristics to enable the remote
provisioning of scalable and measured IT resources in an effective manner. The
following six specific characteristics are common to the majority of cloud
environments:
• on-demand usage
• ubiquitous access
• multitenancy (and resource pooling)
• elasticity
• measured usage
• resiliency
Cloud providers and cloud consumers can assess these characteristics individually and
collectively to measure the value offering of a given cloud platform. Although cloud-
based services and IT resources will inherit and exhibit individual characteristics to
varying extents, usually the greater the degree to which they are supported and utilized,
the greater the resulting value proposition.
On-Demand Usage
A cloud consumer can unilaterally access cloud-based IT resources, giving the cloud
consumer the freedom to self-provision these IT resources. Once configured, usage of the
self-provisioned IT resources can be automated, requiring no further human involvement
by the cloud consumer or cloud provider. This results in an on-demand usage
environment. Also known as “on-demand self-service usage,” this characteristic enables
the service-based and usage-driven features found in mainstream clouds.
Ubiquitous Access
Ubiquitous access represents the ability for a cloud service to be widely accessible.
Establishing ubiquitous access for a cloud service can require support for a range of
devices, transport protocols, interfaces, and security technologies. To enable this level
of access generally requires that the cloud service architecture be tailored to the
particular needs of different cloud service consumers.
Multitenancy (and Resource Pooling)
The characteristic of a software program that enables an instance of the program to
serve different consumers (tenants) whereby each is isolated from the other, is referred
to as multitenancy. A cloud provider pools its IT resources to serve multiple cloud
service consumers by using multitenancy models that frequently rely on the use of
virtualization technologies. Through the use of multitenancy technology, IT resources
can be dynamically assigned and reassigned according to cloud service consumer
demands.
Resource pooling allows cloud providers to pool large-scale IT resources to serve
multiple cloud consumers. Different physical and virtual IT resources are dynamically
assigned and reassigned according to cloud consumer demand, typically followed by
execution through statistical multiplexing. Resource pooling is commonly achieved
through multitenancy technology and therefore encompasses this multitenancy
characteristic.
Elasticity
Elasticity is the automated ability of a cloud to transparently scale IT resources, as
required in response to runtime conditions or as pre-determined by the cloud consumer
or cloud provider. Elasticity is often considered a core justification for the adoption of
cloud computing, primarily due to the fact that it is closely associated with the Reduced
Investment and Proportional Costs benefit. Cloud providers with vast IT resources can
offer the greatest range of elasticity.
Measured Usage
The measured usage characteristic represents the ability of a cloud platform to keep
track of the usage of its IT resources, primarily by cloud consumers. Based on what is
measured, the cloud provider can charge a cloud consumer only for the IT resources
actually used and/or for the timeframe during which access to the IT resources was
granted. In this context, measured usage is closely related to the on-demand
characteristic.
Measured usage is not limited to tracking statistics for billing purposes. It also
encompasses the general monitoring of IT resources and related usage reporting (for
both cloud providers and cloud consumers).
Resiliency
Resilient computing is a form of failover that distributes redundant implementations of
IT resources across physical locations. IT resources can be pre-configured so that if one
becomes deficient, processing is automatically handed over to another redundant
implementation. Within cloud computing, the characteristic of resiliency can refer to
redundant IT resources within the same cloud (but in different physical locations) or
across multiple clouds. Cloud consumers can increase both the reliability and availability
of their applications by leveraging the resiliency of cloud-based IT resources
Cloud Service Models
The cloud computing ecosystem is primarily structured around three core service models:
Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a
Service(SaaS). Each model offers different levels of abstraction and management
responsibility, catering to diverse user needs and technical requirements
• IaaS is the cloud service model that offers a higher level of control compared with an
on-premises solution.
• PaaS makes the process of developing and deploying applications simpler and more
cost-effective.
• SaaS makes collaboration among teams and access to software applications easier.

IaaS (Infrastructure as a Service)

 IaaS is a cloud service model that consists of provisioning and managing
computing resources over the Internet, such as servers, storage, networking, and
virtualization.
 Infrastructure as a Service provides businesses with the technology and capabilities
of high-standard data centers.
 This way, companies delegate the cost and complexity of building and managing
physical servers.
 Companies access their infrastructure via a dashboard or API, but they do not
have to physically manage it.
 This cloud service model offers a lot of flexibility to companies. They can purchase
computing resources on demand, boosting efficiency and scalability.
 So, IaaS can be a real money and time saver.
 IaaS can be used for many purposes, such as deploying web applications, running a
CRM, doing Big Data analysis, backups, or Disaster Recovery plans. Some examples
of IaaS are Stackscale, AWS, and VMware.
 The IaaS market is projected to surpass $481 billion by 2030 (approximately
€473 billion), growing at a compound annual growth rate (CAGR) of 25.3%
between 2021 and 2030.
IaaS benefits
Control. Businesses keep control of their infrastructure.
Cost-efficiency. Resources can be purchased on demand, without big hardware
investments.
Automation. Business can boost productivity, efficiency and security through
automation.
Scalability. Companies can easily grow and add resources according to their needs.
IaaS concerns
 IaaS concerns vary considerably depending on the type of cloud chosen.
 Companies will not leverage the same benefits from a public, private, or hybrid
cloud.
 While vendor lock-in and performance issues might be a big concern in a public
cloud, management and interoperability between environments is one of the top
concerns in a hybrid or multi-cloud environment.
 In addition to that, features vary significantly among providers.
PaaS (Platform as a Service)
 PaaS is a cloud service model that provides a ready-to-use development environment
where developers can focus on writing and executing high-quality code to create
customized applications.
 PaaS is delivered via the web, allowing developers to build scalable and highly
available applications without worrying about the OS, storage, or updates.
 It provides a framework developers can use for developing, managing, distributing,
and testing software applications.
 This cloud service model makes the process of application development simpler and
more cost-effective.
 It integrates web services, database engines, etc., to help developers with app
The PaaS market is forecasted to reach $319 billion by 2030 (approximately €313
billion), growing at a CAGR of 22% between 2021 and 2030.

PaaS benefits
 Easy to use. Simple and cost-effective applications development, testing, and
deployment.
 Productivity. Developers can build scalable and highly available customized
applications easily and with less code.
 Agility. Faster innovation.
 Collaboration. It enhances collaboration among teams spread across diverse
locations.
PaaS concerns
 Data security.
 Interoperability and vendor lock-in.
 Integrations and compatibility.
 Operational limitations.
 Runtime.
SaaS (Software as a Service)
 SaaS is a cloud service model that consists of delivering cloud-based applications to
users over the Internet.
 Software is hosted online and made available to customers on a subscription basis or
for purchase.
 SaaS cloud providers host applications in his network and users can access them
through a browser or app, from different devices.
 Software as a Service is also known as “on-demand software” or “cloud application
services”.
 SaaS providers are responsible for developing, hosting, maintaining and updating
the software.
 Therefore, users only need to login and start using it online, without installing or
hosting any software locally.
 As a result, IT staff do not need to waste time downloading and installing
applications on each employee’s computer.
 However, this also entails that end users do not have much control over it. This lack
of control can be a handicap for some businesses.
 Software as a Service is the most common cloud computing service. We all use some
SaaS products in our daily lives.
 Some examples of SaaS are Google Workspace, Dropbox and Salesforce.
 The SaaS market is expected to reach $702 billion by 2030 (approximately €689
billion), growing at a CAGR of 18.82% between 2021 and 2030.
SaaS benefits
 Efficiency. It allows saving time and money by outsourcing the installation, management and
upgrade of software applications.
 Time saving. IT staff are free to consecrate their time on more valuable, complex tasks.
 Regular updates. Continuous upgrades and UX improvements.
 Accessibility. Users can access the software from anywhere, using any supported device.
SaaS concerns
 Data security.
 Customization and feature limitations.
 Interoperability and vendor lock-in.
 Integration support.
 Performance.
Comparing on-premises, IaaS, PaaS, and SaaS models
 IaaS PaaS SaaS
Computing, storage and Development and
Cloud-based applications.
networking resources. deployment environments.
Accessed via a dashboard Accessed through a browser
Accessed via the web.
or API. or app.
Available for free, on a
Available on a pay-per-use Available on a pay-per-use
subscription basis or for
or pay-as-you-go basis. basis.
purchase.
Network architects and IT
Software developers. End users.
administrators.
Cloud Deployment Models
 Cloud Computing has now become an essential part of modern businesses, offering
flexibility, scalability, and cost-effective solutions.
 However, selecting the most appropriate cloud deployment model is essential to fully
utilize the potential of cloud services.
 Whether you're a small business or a large enterprise, choosing the right cloud model
can affect your security, scalability, and operational efficiency.
 A cloud deployment model fundamentally determines where the infrastructure for
your deployment exists and who owns and controls that infrastructure.
Public Cloud

The public cloud makes it possible for anybody to access systems and services. The
public cloud may be less secure as it is open to everyone. The public cloud is one in
which cloud infrastructure services are provided over the internet to the general people
or major industry groups. The infrastructure in this cloud model is owned by the entity
that delivers the cloud services, not by the consumer. It is a type of cloud hosting that
allows customers and users to easily access systems and services. This form of cloud
computing is an excellent example of cloud hosting, in which service providers supply
services to a variety of customers. In this arrangement, storage backup and retrieval
services are given for free, as a subscription, or on a per-user basis. For example,
Disadvantages of the Public Cloud Model
•Less secure: Public cloud is less secure as resources are public, so there is no
guarantee of high-level security.
•Low customization: It is accessed by many public, so it can't be customized according
to personal requirements.
Advantages of the Public Cloud Model
•Minimal Investment: Because it is a pay-per-use service, there is no substantial
upfront fee, making it excellent for enterprises that require immediate access to
resources.
•No setup cost: The entire infrastructure is fully subsidized by the cloud service
providers, thus there is no need to set up any hardware.
•Infrastructure Management is not required: Using the public cloud does not
necessitate infrastructure management.
•No maintenance: The maintenance work is done by the service provider (not users).
•Dynamic Scalability: To fulfill your company's needs, on-demand resources are
accessible.
Private Cloud

The private cloud deployment model is the exact opposite of the public cloud
deployment model. It's a one-on-one environment for a single user (customer). There is
no need to share your hardware with anyone else. The distinction between
private and public clouds is in how you handle all of the hardware. It is also called the
"internal cloud" & it refers to the ability to access systems and services within a given
border or organization. The cloud platform is implemented in a cloud-based secure
environment that is protected by powerful firewalls and under the supervision of an
organization's IT department. The private cloud gives greater flexibility of control over
cloud resources.
Disadvantages of the Private Cloud Model
•Less scalable: Private clouds are scaled within a certain range as there is less number
of clients.

•Costly: Private clouds are more costly as they provide personalized facilities.
Advantages of the Private Cloud Model
•Better Control: You are the sole owner of the property. You gain complete command
over service integration, IT operations, policies, and user behavior.

•Data Security and Privacy: It's suitable for storing corporate information to which
only authorized staff have access. By segmenting resources within the same
infrastructure, improved access and security can be achieved.

•Supports Legacy Systems: This approach is designed to work with legacy systems
that are unable to access the public cloud.

•Customization: Unlike a public cloud deployment, a private cloud allows a company

to tailor its solution to meet its specific needs.
Hybrid Cloud

By bridging the public and private worlds

with a layer of proprietary software, hybrid
cloud computing gives the best of both
worlds. With a hybrid solution, you may host
the app in a safe environment while taking
advantage of the public cloud's cost savings.
Organizations can move data and applications
between different clouds using a combination
of two or more cloud deployment methods,
depending on their needs.
Advantages of the Hybrid Cloud Model
•Flexibility and control: Businesses with more flexibility can design personalized
solutions that meet their particular needs.
•Cost: Because public clouds provide scalability, you'll only be responsible for paying
for the extra capacity if you require it.
•Security: Because data is properly separated, the chances of data theft by attackers are
considerably reduced.
Disadvantages of the Hybrid Cloud Model
•Difficult to manage: Hybrid clouds are difficult to manage as it is a combination of
both public and private cloud. So, it is complex.
•Slow data transmission: Data transmission in the hybrid cloud takes place through the
public cloud so latency occurs.
Community Cloud

It allows systems and services to be accessible by

a group of organizations. It is a distributed
system that is created by integrating the services
of different clouds to address the specific needs
of a community, industry, or business. The
infrastructure of the community could be shared
between the organization which has shared
concerns or tasks. It is generally managed by a
third party or by the combination of one or more
organizations in the community.
Advantages of the Community Cloud Model
•Cost Effective: It is cost-effective because the cloud is shared by multiple
organizations or communities.
•Security: Community cloud provides better security.
•Shared resources: It allows you to share resources, infrastructure, etc. with multiple
organizations.
•Collaboration and data sharing: It is suitable for both collaboration and data sharing.
Disadvantages of the Community Cloud Model
•Limited Scalability: Community cloud is relatively less scalable as many
organizations share the same resources according to their collaborative interests.
•Rigid in customization: As the data and resources are shared among different
organizations according to their mutual interests if an organization wants some changes
according to their needs they cannot do so because it will have an impact on other
organizations.
Multi-Cloud
We're talking about employing multiple
cloud providers at the same time under this
paradigm, as the name implies. It's similar
to the hybrid cloud deployment approach,
which combines public and private cloud
resources. Instead of merging private and
public clouds, multi-cloud uses many public
clouds. Although public cloud providers
provide numerous tools to improve the
reliability of their services, mishaps still
occur. It's quite rare that two distinct clouds
would have an incident at the same moment.
As a result, multi-cloud deployment
improves the high availability of your
services even more.
Advantages of the Multi-Cloud Model
•You can mix and match the best features of each cloud provider's services to suit the
demands of your apps, workloads, and business by choosing different cloud providers.
•Reduced Latency: To reduce latency and improve user experience, you can choose
cloud regions and zones that are close to your clients.
•High availability of service: It's quite rare that two distinct clouds would have an
incident at the same moment. So, the multi-cloud deployment improves the high
availability of your services.
Disadvantages of the Multi-Cloud Model
•Complex: The combination of many clouds makes the system complex, and
bottlenecks may occur.
•Security issue: Due to the complex structure, there may be loopholes that a hacker can
take advantage hence, which makes the data insecure.
 Community
Factors Public Cloud Private Cloud Hybrid Cloud
Cloud
Complex, requires Complex, requires Complex, requires
Initial Setup Easy a professional a professional a professional
team to setup team to setup team to setup
Scalability and
High High Fixed High
Flexibility
Distributed cost Between public
Cost-Comparison Cost-Effective Costly
among members and private cloud

Reliability Low Low High High

Data Security Low High High High

Data Privacy Low High High High

 REFERENCE

Thomas Erl, Ricardo Puttini, Zaigham Mahmood, “Cloud Computing: Concepts,

Technology & Architecture”, PHI Publications, 2013.
THANK YOU