TUpapers logo TUpapers.com

Explore TUpapers

Study materials and tools in one place.

  • Dashboard
  • Blog
  • Search
  • About

Follow us

TUpapers on Facebook
TUpapers on Instagram
Contact TUpapers on WhatsApp
TUpapers subreddit on Reddit
Student Dashboard Student Dashboard
TUpapers logo TUpapers.com
  • Blog
  • About

Support Us

Your support helps us for further development and maintenance of site and resources!

Bank QR code for payment
eSewa QR code for payment
Khalti QR code for payment

The best way to support TUpapers is by purchasing a Premium Suscription or Notes Every purchase directly funds new features, better study resources, and platform maintenance.

On this chapter

Unit 1: Introduction to Cloud Computing

All Chapters

Dashboard

Select a chapter to start reading

Cloud Computing Notes | BCA Seventh Semester | TU Papers

1 Chapter 1 Preview

No preview available.

Notes for this subject are coming soon — check back later.

Student Dashboard

Continue Reading

Get full notes inside the dashboard, along with other study tools.

Unit 1: Introduction to Cloud Computing [6 Hrs.]

Cloud computing is a model for delivering computing resources such as servers, storage, databases, networking, software, and processing power through a network, usually the Internet. Instead of owning and operating every computing resource locally, users can obtain resources from a cloud provider when needed. This unit covers the foundation of cloud computing, its evolution, characteristics, deployment and service models, storage, infrastructure, service requirements, challenges, applications, and the process organizations follow when adopting cloud technology.

Tested Topics

  1. Cloud adoption — 3x (2026, 2025, 2023)
  2. Cloud computing challenges — 1x (2026)
  3. Cloud computing characteristics (on-demand resource provisioning, scalability & pay-as-you-go) — 1x (2024)
  4. Cloud computing overview and definition — 1x (2024)
  5. Cloud infrastructure — 1x (2026)
  6. Cloud services requirements — 1x (2026)
  7. Cloud Storage and Amazon S3 bucket addressing — 1x (2024)
  8. Evolution of Cloud Computing — 1x (2026)

1.1 Overview of Cloud Computing

Definition

Cloud computing is a computing model that provides shared computing resources such as servers, storage, applications, databases, and networks over the Internet whenever users need them. These resources can normally be obtained quickly, scaled according to demand, and paid for according to usage.


Instead of buying a powerful computer or maintaining a private server for every requirement, a user connects to computing resources operated elsewhere. A student using online file storage, a company renting a virtual server, and a business using web-based accounting software are all using forms of cloud computing.

Detailed Explanation

Traditional information technology infrastructure requires an organization to purchase physical servers, install software, provide storage, maintain networking equipment, arrange backup systems, and employ people to manage those resources. This approach gives direct control, but it also requires significant initial investment and continuous maintenance.

Cloud computing changes this model. Computing resources are operated in provider-managed data centers and delivered to customers through a network. Customers request the resources they require without needing to know the physical machine on which each workload is running.

Basic Working of Cloud Computing

A typical cloud interaction follows this sequence:

User or application request → Internet or private network → Cloud service platform → Computing, storage, or application resource → Result returned to the user

The provider manages the underlying infrastructure while the amount of responsibility handled by the customer depends on the cloud service model being used.

Main Elements of a Cloud Environment

  • Client: the computer, smartphone, browser, or application used to access the cloud.
  • Network: the communication path connecting users to cloud resources.
  • Cloud provider: the organization operating and delivering cloud resources.
  • Compute resources: processors and memory used to execute workloads.
  • Storage: systems used to retain files, objects, databases, and backups.
  • Virtualization: technology that allows physical computing resources to be divided into multiple logical resources.
  • Management platform: software used for provisioning, monitoring, security, billing, and automation.

Traditional Computing and Cloud Computing

BasisTraditional ComputingCloud Computing
InfrastructureOrganization purchases and operates its own hardware.Resources may be obtained from a cloud provider.
Initial costUsually requires significant capital expenditure.Can reduce initial hardware investment.
ProvisioningNew hardware may require days or weeks to purchase and configure.Resources can often be provisioned within minutes.
ScalingRequires purchasing or removing physical equipment.Resources can increase or decrease according to demand.
MaintenanceOrganization manages physical infrastructure.Provider manages part or all of the underlying infrastructure.
ChargingCost is largely based on owned capacity.Many services use usage-based pricing.

Let's Clarify

A college that expects a huge increase in website traffic during result publication could purchase enough physical servers to handle the busiest day of the year. Those servers might remain underused for most of the year. With cloud computing, additional computing capacity can be activated during the result period and reduced afterward. The infrastructure therefore follows demand more closely.

Summary

  • Cloud computing delivers computing resources through a network rather than requiring every resource to be owned locally.
  • Cloud resources include computing power, networking, storage, databases, platforms, and software applications.
  • Users request resources while cloud providers operate the underlying infrastructure according to the chosen service model.
  • Cloud computing supports faster provisioning and flexible resource consumption compared with purely physical infrastructure.
  • Its foundation includes networks, data centers, virtualization, automation, storage, and management systems.

Test Yourself

  1. How does cloud computing differ from the traditional approach of maintaining local computing infrastructure?
  2. Define cloud computing. (2024)

Hints:

  1. Traditional computing mainly relies on organization-owned hardware; cloud computing provides shared computing resources through a network with flexible provisioning and scaling.
  2. Cloud computing is a model that provides configurable computing resources such as servers, storage, networks, and applications over a network on demand.

1.2 Evolution of Cloud Computing

Definition

The evolution of cloud computing is the gradual development of computing technologies and service models that made shared, remotely accessible, scalable, and on-demand computing possible.


Cloud computing did not appear as one completely new invention. It developed from earlier ideas such as centralized mainframes, time-sharing, computer networking, distributed computing, virtualization, utility computing, web technologies, and large-scale data centers.

Detailed Explanation

Modern cloud systems combine technologies developed over several decades. Each stage solved a limitation of the previous computing model and contributed an idea that is now fundamental to cloud computing.

1. Mainframe and Centralized Computing

Early organizations relied on powerful mainframe computers. A mainframe was expensive, so many users shared the processing power of one central system through terminals.

This introduced an important cloud idea: many users can share centralized computing resources instead of each user requiring a separate powerful computer.

2. Time-Sharing Systems

Time-sharing allowed multiple users to interact with a computer apparently at the same time. The processor divided its time among different tasks and users.

Time-sharing improved resource utilization and established the idea of allocating computing capacity dynamically among multiple consumers.

3. Personal Computing and Client-Server Computing

The growth of personal computers shifted processing from centralized mainframes toward individual machines. Later, client-server computing divided work between client devices and centralized servers.

A client could request information or services from a server over a network. This became an important foundation for Internet-based applications.

4. Computer Networks and the Internet

As networking technologies developed, geographically separated computers could communicate and exchange information. The expansion of the Internet made it possible to access services hosted in remote locations from almost anywhere.

Networking → remote access → Internet services → global delivery of computing resources

5. Distributed and Cluster Computing

In distributed computing, multiple networked computers cooperate to solve problems or deliver services. Cluster computing connects multiple machines so that they can operate together as a more powerful system.

These approaches demonstrated that a workload does not always have to run on one physical computer.

6. Grid Computing

Grid computing coordinates computing resources from multiple locations or organizations to solve large computational problems. Resources can be distributed geographically and combined for a common task.

Grid computing contributed concepts of distributed resource sharing and large-scale workload execution, although cloud computing later added stronger service abstraction, elasticity, automation, and commercial delivery models.

7. Virtualization

Virtualization allows one physical computer to host multiple isolated virtual computing environments. A software layer called a hypervisor allocates processor, memory, storage, and other resources to different Virtual Machines (VMs).

Virtualization became one of the strongest technical foundations of cloud infrastructure because cloud providers could divide large physical servers into flexible pools of virtual resources.

Physical server → Hypervisor → Multiple VMs → Resources allocated according to workload

8. Utility Computing

Utility computing introduced the business idea that computing could be consumed in a manner similar to electricity or other utilities. Users obtain capacity when required and pay according to consumption rather than purchasing every resource permanently.

This concept directly influenced the pay-as-you-go pricing model used by many cloud services.

9. Web Services and Service-Oriented Architecture

Web services allowed software systems to communicate using standardized network interfaces. Service-Oriented Architecture (SOA) organized software functionality into reusable services that could interact through defined interfaces.

These developments helped applications become less dependent on one physical system and easier to distribute over networks.

10. Large Data Centers and Modern Cloud Platforms

Advances in commodity servers, high-speed networks, distributed storage, virtualization, automation, monitoring, and Internet connectivity made it possible to operate enormous data centers efficiently.

Providers could pool these resources and expose them through web portals and Application Programming Interfaces (APIs). Customers could then create servers, allocate storage, deploy applications, and manage services programmatically.

Evolution at a Glance

DevelopmentContribution to Modern Cloud Computing
Mainframe computingCentralized shared resources
Time-sharingMultiple users sharing computing capacity
Client-server computingNetwork-based service requests
InternetGlobal remote connectivity
Distributed and cluster computingWorkloads distributed across multiple computers
Grid computingLarge-scale distributed resource sharing
VirtualizationLogical resources separated from physical hardware
Utility computingMetered, consumption-based computing
Web services and SOAStandardized network-accessible software services
Automation and large data centersFast provisioning, elasticity, and modern cloud platforms

Let's Clarify

The evolution resembles the development of public transportation. Owning a private vehicle means purchasing and maintaining capacity for yourself. Shared transportation lets many people use common infrastructure when required. Cloud computing applies a related idea to computing resources, but adds automation, virtualization, Internet access, measurement, and rapid scaling.

Summary

  • Cloud computing evolved gradually from centralized, networked, distributed, and virtualized computing technologies.
  • Mainframes and time-sharing introduced shared computing resources.
  • Networking and the Internet enabled remote delivery of services.
  • Distributed, cluster, and grid systems showed how workloads and resources could span multiple computers.
  • Virtualization enabled flexible pools of isolated computing resources, while utility computing introduced consumption-based charging.
  • Automation, web services, and large data centers combined these developments into modern cloud platforms.

Test Yourself

  1. How did virtualization and utility computing contribute differently to cloud computing?
  2. Describe the evolution of Cloud Computing with key technological developments that led to modern cloud computing. [5] (2026)

Hints:

  1. Virtualization provides the technical ability to divide and allocate hardware resources; utility computing provides the consumption and payment model based on usage.
  2. Trace mainframes and time-sharing → networking and client-server systems → distributed/grid computing → virtualization → utility computing → web services, automation, and large cloud data centers.

1.3 Characteristics of Cloud Computing

Definition

Characteristics of cloud computing are the features that distinguish cloud services from ordinary remotely hosted computing. Core characteristics include on-demand access, broad network availability, resource pooling, rapid elasticity, and measured usage.


A cloud system does more than keep a server somewhere else. Users can request resources when required, share large resource pools, reach services through networks, increase or decrease capacity, and have usage measured for management or billing.

Detailed Explanation

1. On-Demand Self-Service and Resource Provisioning

On-demand self-service means a customer can obtain computing resources when needed without requiring manual interaction with the provider for every request.

Resource provisioning is the process of allocating resources such as processor capacity, memory, storage, databases, or virtual servers to a workload.

For example, a developer can request a new VM through a provider portal or API. The platform automatically selects suitable infrastructure, allocates resources, configures the VM, and makes it available.

Request → Automated provisioning system → Resource allocated → Service becomes available

2. Broad Network Access

Broad network access means cloud services are available through network connections and can be accessed using standard mechanisms from devices such as laptops, desktops, smartphones, tablets, and servers.

This characteristic allows applications and data to remain accessible without requiring the user to be physically close to the underlying infrastructure.

3. Resource Pooling

Resource pooling means a cloud provider combines computing, storage, and networking resources into shared pools that can serve many customers.

Resources are assigned and reassigned according to demand. Customers normally interact with logical resources rather than choosing a particular physical processor, disk, or server.

A common cloud approach is multi-tenancy, where infrastructure serves multiple customers while logical isolation keeps their workloads and data separated.

4. Rapid Elasticity and Scalability

Scalability is the ability of a system to handle increasing or decreasing workloads by changing the amount of computing resources available.

Elasticity goes further. It is the ability to increase and decrease resources dynamically as workload demand changes.

Two common forms of scaling are:

  • Vertical scaling: increasing the capacity of an existing machine, such as adding more processor power or memory.
  • Horizontal scaling: adding more machines or service instances to share the workload.
FeatureVertical ScalingHorizontal Scaling
Main actionIncrease capacity of one system.Add additional systems or instances.
ExampleIncrease a VM from 4 GB to 16 GB memory.Increase a web service from 2 instances to 10 instances.
Common descriptionScale up or downScale out or in

Elasticity is particularly useful for variable workloads. An online shopping service may use ordinary capacity during normal periods and automatically increase resources during a major sale.

5. Measured Service and Pay-As-You-Go

Measured service means cloud platforms monitor resource consumption such as processing time, storage capacity, data transfer, requests, or service usage.

A pay-as-you-go pricing model charges customers according to the cloud resources they consume rather than requiring them to purchase all capacity permanently in advance.

For example, if an organization uses a virtual server for a limited period, the provider can measure that consumption and calculate the charge according to the service's pricing rules.

Scalability, Elasticity, and Pay-As-You-Go Together

These features reinforce one another:

Demand rises → More resources provisioned → Usage increases → Metering records additional consumption → Demand falls → Resources are reduced → Future consumption decreases

Let's Clarify

Consider an online university result portal. During ordinary weeks, relatively few students access it. When results are published, thousands may arrive at once. Scalability allows the system to support greater load. Elasticity allows resources to expand temporarily and shrink afterward. Measured service records the resources consumed during that period.

Common Mistake

Scalability and elasticity are related but not identical. Scalability means a system can handle different workload levels by changing capacity. Elasticity emphasizes dynamically matching capacity to changing demand, often automatically.

Summary

  • On-demand self-service lets customers obtain cloud resources without repeated manual provider intervention.
  • Broad network access makes services reachable through standard networks from different client devices.
  • Resource pooling allows provider infrastructure to serve multiple customers efficiently.
  • Scalability changes system capacity, while elasticity dynamically matches resources to changing demand.
  • Measured service records resource consumption and supports usage-based management and billing.
  • Pay-as-you-go pricing connects cloud cost with the amount of service consumed.

Test Yourself

  1. Differentiate between scalability and elasticity with an example.
  2. Explain on-demand resource Provisioning, Scalability and pay-as-you- go pricing model. (2024)

Hints:

  1. Scalability is the ability to handle different workload levels by changing capacity; elasticity dynamically increases or decreases that capacity as demand changes.
  2. On-demand provisioning allocates resources when requested; scalability changes available capacity; pay-as-you-go charges according to measured resource consumption.

1.4 Types of cloud and its Cloud services

Definition

Cloud computing can be classified in two major ways: deployment models, which describe where and for whom cloud infrastructure is operated, and service models, which describe the level of computing capability provided to customers.


The deployment model answers, “Whose cloud environment is this and who can use it?” The service model answers, “How much of the computing system does the provider manage for the customer?”

Detailed Explanation

Cloud Deployment Models

1. Public Cloud

A public cloud provides cloud services through infrastructure operated by a cloud provider for multiple customers. Customers consume services without owning the underlying physical data center.

It is suitable when organizations want rapid access to scalable infrastructure without building a complete private environment.

2. Private Cloud

A private cloud is a cloud environment dedicated to a single organization. It may be operated within the organization's facilities or hosted by a third party.

Private clouds provide greater organizational control over infrastructure configuration, security policies, and resource management, but the organization normally accepts more responsibility and cost.

3. Community Cloud

A community cloud is designed for several organizations that share similar requirements, such as security, regulatory, operational, or mission requirements.

For example, a group of institutions operating under similar compliance requirements may share a cloud environment designed specifically for that community.

4. Hybrid Cloud

A hybrid cloud combines two or more distinct cloud environments, commonly private and public cloud, while allowing workloads or data to move or interact between them.

An organization might keep sensitive systems in a private environment while using public cloud resources for a public-facing website or temporary extra capacity.

ModelMain IdeaControlTypical Use
Public CloudProvider-operated shared cloudLess direct infrastructure controlGeneral-purpose scalable services
Private CloudDedicated to one organizationHigh organizational controlSensitive or organization-specific workloads
Community CloudShared by organizations with common requirementsShared governanceSector or mission-specific environments
Hybrid CloudCombination of distinct cloud environmentsMixedWorkloads needing both private and public capabilities

Cloud Service Models

1. Infrastructure as a Service (IaaS)

Infrastructure as a Service (IaaS) provides fundamental computing resources such as virtual machines, networks, and storage.

The provider manages the physical data center, servers, storage hardware, networking, and virtualization layer. The customer generally manages the operating system, applications, configurations, and data running inside the provided infrastructure.

Examples include renting virtual servers and virtual networks for hosting applications.

2. Platform as a Service (PaaS)

Platform as a Service (PaaS) provides a managed environment in which customers can develop, deploy, and run applications without directly managing most underlying infrastructure.

The provider manages infrastructure, operating systems, and platform components. Developers concentrate mainly on application code, application configuration, and data.

3. Software as a Service (SaaS)

Software as a Service (SaaS) provides complete software applications over a network. Users normally access the application using a browser, mobile application, or client interface.

The provider manages the application and underlying platform and infrastructure. Customers primarily configure and use the software.

FeatureIaaSPaaSSaaS
What customer receivesVirtual infrastructureManaged application platformReady-to-use application
Customer managesOperating system, applications, data, many configurationsApplication code, application settings, dataMostly application usage and user-level configuration
Provider responsibilityPhysical infrastructure and virtualizationInfrastructure plus operating environmentAlmost the complete technical stack
Typical userSystem administrators and infrastructure teamsApplication developersEnd users and organizations

The responsibility generally shifts toward the provider as we move from IaaS to PaaS to SaaS.

IaaS → More customer control and management responsibility
PaaS → Focus on application development
SaaS → Focus mainly on using the application

Cloud computing ecosystem and cloud service environment

Let's Clarify

Suppose a team wants to publish a web application. With IaaS, it can rent virtual machines and manage the operating system and application itself. With PaaS, it can deploy application code onto a managed platform. With SaaS, there is no application-development task for the customer because the finished software itself is the service being consumed.

Summary

  • Deployment models describe how cloud infrastructure is organized and who uses it.
  • Public, private, community, and hybrid clouds are the major deployment models.
  • IaaS provides computing infrastructure such as virtual machines, storage, and networking.
  • PaaS provides a managed environment for developing and running applications.
  • SaaS delivers complete applications to users over a network.
  • Moving from IaaS toward SaaS generally increases the provider's management responsibility.

Test Yourself

  1. Differentiate public, private, community, and hybrid cloud deployment models.
  2. Compare IaaS, PaaS, and SaaS according to provider and customer responsibilities.
  3. Why might an organization choose a hybrid cloud instead of relying entirely on a public cloud?

Hints:

  1. Compare ownership or access, control, intended users, and typical workload requirements.
  2. IaaS gives virtual infrastructure, PaaS gives a managed development platform, and SaaS gives a finished application. Provider responsibility increases from IaaS to SaaS.
  3. A hybrid model allows selected workloads or data to remain in a controlled environment while other workloads use public-cloud scalability and services.

1.5 Benefits and challenges of cloud computing

Definition

Benefits of cloud computing are the technical and business advantages gained by consuming computing resources as flexible services. Challenges of cloud computing are the technical, security, financial, operational, and organizational difficulties that can arise when applications and data depend on cloud environments.


Cloud computing can make infrastructure faster to obtain and easier to scale, but moving systems outside a traditional local environment also introduces concerns such as security, availability, provider dependence, compliance, and cost management.

Detailed Explanation

Benefits of Cloud Computing

  • Reduced initial infrastructure investment: organizations can use provider infrastructure instead of purchasing all computing capacity before it is needed.
  • Rapid provisioning: servers, databases, storage, and other services can often be created much faster than purchasing and installing physical equipment.
  • Scalability: resources can be increased as the workload grows.
  • Elasticity: resources can also decrease when demand falls, helping capacity follow actual workload.
  • Measured usage: consumption can be monitored and associated with departments, workloads, or customers.
  • Global accessibility: cloud-hosted services can be made available to users in different geographic regions through network connectivity.
  • High availability options: cloud architectures can distribute services across multiple systems or locations to reduce dependence on one component.
  • Backup and disaster recovery support: cloud storage and geographically distributed infrastructure can support backup and recovery strategies.
  • Faster experimentation: teams can create temporary development or testing environments without purchasing permanent hardware.
  • Managed services: providers can operate parts of the technical stack, reducing the amount of infrastructure work performed directly by the customer.

Challenges of Cloud Computing

1. Security and Privacy

Organizations may store sensitive information on systems managed partly or entirely by an external provider. Security requires proper identity management, access control, encryption, network protection, logging, and secure configuration.

2. Internet and Network Dependency

Most cloud services depend on reliable network connectivity. Slow, unstable, or unavailable connections can affect access to cloud-hosted applications and data.

3. Availability and Service Outages

No computing system can guarantee that failures will never occur. Provider outages, network failures, software defects, or configuration errors can interrupt cloud services.

Organizations therefore need suitable redundancy, recovery plans, and service-level requirements.

4. Vendor Lock-In

Vendor lock-in occurs when an application becomes strongly dependent on one provider's proprietary services, interfaces, data formats, or operational tools, making migration to another environment difficult or expensive.

5. Cost Management

Usage-based charging can improve flexibility, but poorly controlled resource consumption may create unexpectedly high bills. Unused virtual machines, excessive storage, unnecessary data transfers, and overprovisioned services can increase cost.

6. Compliance and Legal Requirements

Organizations may need to obey rules governing privacy, data protection, auditing, record retention, or the geographic location of data. Cloud deployment must therefore be aligned with applicable organizational and legal requirements.

7. Data Migration

Moving large databases and applications to a cloud environment can require substantial planning. Challenges include transfer time, compatibility, downtime, data integrity, application dependencies, and testing.

8. Skills and Organizational Change

Cloud platforms introduce new tools, architectures, security models, automation methods, and cost-management practices. Existing staff may require training, and development and operations teams may need different processes.

Benefits and Challenges Compared

Cloud CapabilityPotential BenefitRelated Challenge
Internet-based accessAccess from many locationsDependence on network availability
Resource elasticityCapacity follows workloadUncontrolled scaling can increase cost
Provider-managed infrastructureLess physical infrastructure managementReduced direct control and provider dependence
Large shared platformsEconomies of scale and broad service choiceSecurity and compliance require careful configuration
Managed proprietary servicesFaster application developmentPossible vendor lock-in

Common Mistake

Moving to the cloud does not automatically remove security responsibility from the customer. The exact division of responsibility depends on the service model. For example, an IaaS customer usually has much more responsibility for operating-system and application security than a SaaS user.

Summary

  • Cloud computing can reduce initial infrastructure requirements and accelerate resource provisioning.
  • Scalability, elasticity, managed services, backup options, and global accessibility are major benefits.
  • Security, privacy, availability, network dependency, and compliance remain significant concerns.
  • Usage-based pricing requires active cost monitoring because uncontrolled consumption can increase expenses.
  • Migration complexity, vendor lock-in, and shortages of cloud skills can affect successful adoption.

Test Yourself

  1. How can a feature of cloud computing become both a benefit and a challenge?
  2. What are the challenges on cloud computing? Explain cloud services requirements and cloud infrastructure in detail. [3+4+3] (2026)

Hints:

  1. Elastic scaling improves capacity management but can increase spending if uncontrolled; provider-managed services reduce maintenance but may increase dependency on a provider.
  2. For the challenge part, cover security/privacy, availability and network dependency, vendor lock-in, cost control, compliance, migration complexity, and required skills.

1.6 Applications cloud computing

Definition

Applications of cloud computing are practical uses of remotely delivered computing, storage, networking, platforms, and software services in personal, educational, commercial, scientific, and organizational activities.


Cloud computing is used whenever people or organizations need computing resources without operating every underlying system themselves. It supports activities ranging from storing a personal file online to running large business applications and data-processing platforms.

Detailed Explanation

1. Data Storage and Backup

Cloud storage can hold documents, images, videos, databases, application data, and backups. Users can access data through networks while providers manage the physical storage infrastructure.

2. Website and Application Hosting

Websites and applications can run on cloud virtual machines, containers, managed platforms, databases, and content-delivery systems. Resources can be increased when application traffic grows.

3. Software Delivery

SaaS applications deliver complete software through the Internet. Examples of application categories include email, office productivity, accounting, collaboration, customer management, and project management.

4. Education and E-Learning

Cloud platforms can support online classes, learning management systems, digital libraries, shared documents, online examinations, student portals, and virtual development laboratories.

A university can provide learning resources centrally so that students and teachers can access the same systems from different locations.

5. Business Collaboration

Teams can use cloud-based document sharing, communication, conferencing, calendars, and project systems. Cloud synchronization allows authorized users to work with updated information across locations.

6. Development and Testing

Developers can create temporary servers, databases, and testing environments when needed. Environments can be reproduced using automation and removed after testing, avoiding permanent hardware allocation.

7. Data Analytics

Cloud platforms can provide large computing and storage capacity for analyzing substantial datasets. Organizations can use managed databases, data warehouses, processing systems, and visualization platforms without building every component locally.

8. Artificial Intelligence and Machine Learning

Cloud platforms can provide specialized computing resources and managed services for training and using Artificial Intelligence (AI) and Machine Learning (ML) models.

9. Disaster Recovery

Organizations can replicate applications or backups to remote cloud locations. If the primary environment fails, cloud-based recovery resources can help restore services and data.

10. E-Commerce

Online stores experience changing demand. Cloud infrastructure can host websites, databases, payment-related application components, product systems, analytics, and scalable backend services.

11. Media Streaming and Content Delivery

Cloud platforms can store and process video, audio, and images while distributed delivery systems help serve content to users in different locations.

12. Internet of Things Applications

Internet of Things (IoT) devices such as sensors and smart machines can transmit data to cloud platforms for storage, analysis, monitoring, and remote control.

AreaCloud Application
EducationLearning platforms, shared documents, student systems
BusinessCollaboration, customer systems, enterprise applications
Software developmentDevelopment, testing, deployment environments
Data managementStorage, backup, databases, analytics
AI and MLModel training, inference, managed AI services
MediaStreaming, encoding, large-scale content delivery
IoTDevice communication, data collection, analysis

Summary

  • Cloud computing is used for storage, backup, application hosting, software delivery, and collaboration.
  • Educational institutions can use cloud systems for e-learning, student services, shared resources, and virtual laboratories.
  • Cloud platforms provide temporary and scalable development and testing environments.
  • Data analytics, AI, ML, and IoT workloads benefit from scalable computing and storage capacity.
  • Cloud infrastructure also supports disaster recovery, e-commerce, media streaming, and global service delivery.

Test Yourself

  1. Explain any five major applications of cloud computing.
  2. How can cloud computing support both education and software development?

Hints:

  1. Suitable applications include storage and backup, web hosting, SaaS, collaboration, analytics, AI and ML, disaster recovery, IoT, e-commerce, and media delivery.
  2. Education uses cloud systems for learning platforms, shared resources, and virtual labs; developers use on-demand environments for coding, testing, databases, and deployment.

1.7 Cloud Storage

Definition

Cloud storage is a service that stores digital data on provider-managed storage infrastructure and makes that data accessible through a network.


Instead of keeping every file on the storage device inside one computer, data can be stored in remote data centers. Users or applications retrieve it using web interfaces, applications, or APIs.

Detailed Explanation

A cloud storage system typically uses many physical storage devices distributed across provider infrastructure. The provider exposes these resources as storage services while handling much of the physical capacity management, hardware replacement, availability, and expansion.

Major Cloud Storage Models

1. Object Storage

Object storage stores data as independent objects. Each object generally contains the data itself, metadata describing the object, and a unique key used to identify it.

Object storage works well for images, videos, backups, archives, static website assets, application files, logs, and large unstructured datasets.

2. Block Storage

Block storage divides storage into fixed-sized blocks that can be attached to computing systems. An operating system can format the blocks with a file system and use them similarly to a disk.

It is commonly used for virtual-machine disks and workloads requiring disk-like storage.

3. File Storage

File storage organizes data into files and folders using a hierarchical structure. Multiple systems can access shared directories through supported network file protocols.

Storage TypeOrganizationTypical Use
Object StorageObjects identified by keysMedia, backups, static files, logs
Block StorageBlocks presented as disk-like volumesVM disks, databases, operating systems
File StorageFiles and foldersShared directories and traditional file workloads

Amazon Simple Storage Service and Buckets

Amazon Simple Storage Service (Amazon S3) is an object-storage service. In S3, a bucket is a container used to organize and store objects.

An S3 object is identified using information including:

  • Bucket name: identifies the bucket that contains the object.
  • Object key: identifies an individual object inside the bucket.
  • Region and endpoint information: may be used when constructing network addresses for a bucket or object.

Suppose a bucket is named college-notes and it contains an object with the key cloud/unit1.pdf. A conceptual S3 resource representation is:

s3://college-notes/cloud/unit1.pdf

Amazon S3 Bucket and Object Addressing

A common virtual-hosted-style S3 URL follows this general form:

https://bucket-name.s3.region-code.amazonaws.com/object-key

Using the example bucket and object:

https://college-notes.s3.region-code.amazonaws.com/cloud/unit1.pdf

Here:

  • college-notes identifies the bucket.
  • region-code represents the relevant service region identifier.
  • cloud/unit1.pdf is the object key.

Older S3 documentation and some endpoint situations also use a path-style concept where the bucket name appears in the URL path. Virtual-hosted-style addressing is the normal pattern for general modern S3 object addressing.

Amazon S3 bucket and object addressing structure

Advantages of Cloud Storage

  • Elastic capacity: storage can grow without installing local disks for every increase.
  • Network accessibility: authorized users and applications can access stored resources remotely.
  • Durability options: providers can maintain redundant copies or use distributed storage mechanisms.
  • Backup support: cloud storage can serve as a destination for backups and archives.
  • Integration: applications can interact with storage through APIs.
  • Measured usage: storage consumption can be monitored and charged according to service pricing.

Let's Clarify

A bucket is not the same as an ordinary physical disk. It is a logical container in an object-storage system. Objects are addressed using their bucket and key rather than by treating the bucket as a traditional local hard-drive partition.

Summary

  • Cloud storage stores data on provider-managed infrastructure and makes it available through network interfaces.
  • The major storage models are object, block, and file storage.
  • Object storage manages data as objects identified by unique keys and metadata.
  • Amazon S3 is an object-storage service in which buckets act as logical containers for objects.
  • An S3 object can be identified through its bucket name and object key.
  • Virtual-hosted-style S3 addressing places the bucket name as part of the service hostname.

Test Yourself

  1. Differentiate object storage, block storage, and file storage.
  2. What is bucket in Amazon simple storage service? How addressing of a bucket is done? (2024)

Hints:

  1. Object storage uses objects and keys; block storage presents disk-like blocks or volumes; file storage organizes data into hierarchical files and folders.
  2. An S3 bucket is a logical container for objects. A common address pattern is https://bucket-name.s3.region-code.amazonaws.com/object-key.

1.8 Cloud services requirements

Definition

Cloud service requirements are the technical, operational, security, performance, legal, and management conditions that a cloud service must satisfy to support users and applications effectively.


Choosing a cloud service is not only about finding computing power. The service must also meet requirements for availability, performance, security, scalability, data protection, interoperability, management, cost, and organizational policies.

Detailed Explanation

1. Availability

Availability describes whether a service remains accessible when users require it. Critical systems may need redundancy across multiple servers or locations so that failure of one component does not immediately stop the entire service.

2. Reliability

Reliability is the ability of a system to operate correctly and consistently over time. Reliable cloud services require fault handling, monitoring, suitable architecture, and tested recovery procedures.

3. Scalability and Elasticity

The cloud environment should support the expected workload and allow additional resources to be allocated when demand increases. For variable workloads, the system may also need to decrease unnecessary capacity when demand falls.

4. Performance

Performance requirements may include processing capacity, application response time, storage performance, network bandwidth, and latency.

A cloud service with sufficient capacity can still be unsuitable if network latency makes the application too slow for its users.

5. Security

Cloud security requirements commonly include:

  • Authentication: verifying the identity of a user or system.
  • Authorization: deciding what an authenticated identity is allowed to do.
  • Encryption: protecting data from unauthorized reading.
  • Network security: controlling traffic entering and leaving cloud resources.
  • Logging and monitoring: recording activity and detecting suspicious behavior.
  • Data protection: preventing unauthorized loss, modification, or disclosure of information.

6. Privacy and Compliance

Organizations may need controls for data privacy, auditing, retention, geographic location, and regulatory requirements. The provider's capabilities must support the organization's obligations.

7. Interoperability

Interoperability is the ability of different systems or services to communicate and work together. Cloud services commonly need standard interfaces and compatible protocols to exchange information with existing systems.

8. Portability

Portability is the ability to move applications or data between environments with manageable effort. Greater portability can reduce dependence on one provider's proprietary technology.

9. Manageability and Monitoring

Administrators need tools to configure resources, track health, inspect performance, manage access, review logs, and understand usage.

10. Backup and Disaster Recovery

Important cloud workloads need appropriate mechanisms for backup, replication, restoration, and recovery after failures. Requirements should identify acceptable data loss and acceptable recovery time.

11. Service-Level Requirements

A Service-Level Agreement (SLA) is an agreement that describes expected service commitments and responsibilities. Depending on the service, it may address availability, support, performance targets, service credits, or other measurable commitments.

12. Cost and Metering

Organizations need transparent information about resource consumption and pricing. Cost requirements may include budgets, spending alerts, resource tagging, cost allocation, and policies for removing unused resources.

13. Network Connectivity

Because cloud resources are accessed through networks, bandwidth, reliability, latency, routing, and connectivity between cloud and local environments must meet application requirements.

RequirementMain Question
AvailabilityCan users reach the service when required?
PerformanceIs the service fast enough for the workload?
ScalabilityCan capacity grow with demand?
SecurityAre systems, identities, and data properly protected?
ComplianceDoes the solution satisfy applicable obligations?
InteroperabilityCan it communicate with other systems?
PortabilityCan workloads or data be moved if necessary?
ManageabilityCan administrators monitor and control the environment?
RecoveryCan service and data be restored after failure?
CostCan consumption and spending be measured and controlled?

Let's Clarify

A technically powerful cloud service may still fail an organization's requirements. A hospital system, banking application, video-streaming platform, and student portal have different expectations for security, latency, recovery, compliance, and cost. Requirements therefore describe what the service must achieve, not merely which technology it uses.

Summary

  • Cloud requirements convert organizational and application needs into conditions a cloud service must satisfy.
  • Core technical requirements include availability, reliability, scalability, performance, and network connectivity.
  • Security requirements cover identity, access control, encryption, monitoring, and data protection.
  • Interoperability and portability affect integration and the ability to move workloads or data.
  • SLAs, monitoring, backup, recovery, compliance, and cost management are important operational requirements.

Test Yourself

  1. Why should cloud service requirements be defined before selecting a cloud solution?
  2. What are the challenges on cloud computing? Explain cloud services requirements and cloud infrastructure in detail. [3+4+3] (2026)

Hints:

  1. Requirements establish the expected availability, performance, security, compliance, integration, recovery, and cost conditions against which solutions can be evaluated.
  2. For cloud service requirements, explain availability, reliability, scalability, performance, security, privacy/compliance, interoperability, portability, monitoring, SLA, recovery, connectivity, and cost.

1.9 cloud and dynamic infrastructure

Definition

Cloud infrastructure is the collection of physical and virtual computing, storage, networking, virtualization, management, and security resources used to provide cloud services. Dynamic infrastructure is infrastructure whose resources can be automatically provisioned, configured, scaled, reassigned, and monitored as workload conditions change.


A traditional server environment can be relatively fixed: one application receives a particular machine and capacity changes require manual work. Dynamic cloud infrastructure treats capacity as a configurable pool. Software can allocate and release resources according to policies and workload demand.

Detailed Explanation

Components of Cloud Infrastructure

1. Data Centers

A data center is a facility containing computing, storage, networking, power, cooling, and supporting systems. Cloud providers may operate many data centers to provide capacity, redundancy, and geographic distribution.

2. Compute Infrastructure

Compute infrastructure includes physical servers and logical computing environments used to execute workloads. Virtual machines and containers can provide isolated environments above the physical hardware.

3. Storage Infrastructure

Storage infrastructure retains application data, object data, databases, backups, VM disks, logs, and other digital information. Cloud platforms may expose object, block, file, and managed database storage services.

4. Network Infrastructure

Cloud networking connects users, servers, storage systems, data centers, and external networks. Components can include physical switches and routers as well as virtual networks, subnets, routing rules, load balancers, gateways, and firewalls.

5. Virtualization Layer

Virtualization separates logical computing resources from physical hardware. A hypervisor can divide one server into several VMs, each with allocated processing power, memory, storage, and networking.

6. Management and Orchestration

Management tools configure and monitor cloud resources. Orchestration coordinates multiple automated operations so that complete environments can be created and managed consistently.

For example, an orchestration process may create a virtual network, several server instances, a load balancer, storage, and monitoring rules as one coordinated deployment.

7. Security Infrastructure

Security infrastructure includes identity systems, access policies, encryption services, network controls, security monitoring, key management, logging, and other protective mechanisms.

How Dynamic Cloud Infrastructure Works

This one has several moving parts, so the sequence matters.

Step 1: Workload Demand Is Observed

Monitoring systems collect information such as processor utilization, memory usage, request rate, response time, storage consumption, or queue length.

Step 2: A Policy or Request Triggers a Change

A user may request additional resources directly, or an automated policy may detect that a workload has crossed a defined threshold.

Step 3: Resources Are Provisioned

The cloud management platform identifies available capacity and creates or allocates suitable resources.

Step 4: Configuration Is Applied

Networking, storage, software configuration, access permissions, and monitoring can be attached to the new resource automatically.

Step 5: Traffic or Work Is Distributed

New capacity becomes part of the active environment. A load balancer or workload scheduler may begin directing tasks to it.

Step 6: Usage Is Monitored

The system continues observing workload and performance conditions.

Step 7: Unnecessary Capacity Is Released

When workload decreases, policies can remove extra instances or reduce allocated capacity.

Monitor → Detect demand → Provision → Configure → Use → Measure → Scale or release

Dynamic cloud infrastructure and automated resource provisioning

Role of Virtualization in Dynamic Infrastructure

Virtualization allows logical machines to be created more quickly than purchasing and installing new physical servers. It also improves resource utilization because several isolated workloads can share a physical machine.

Modern cloud platforms may also use containers and other forms of abstraction, but the central principle remains the same: workloads interact with logical resources while management software controls how those resources map to physical infrastructure.

Static and Dynamic Infrastructure

BasisStatic InfrastructureDynamic Cloud Infrastructure
ProvisioningOften manualCan be automated
CapacityMostly predeterminedCan change according to demand
Resource allocationRelatively fixedResources can be reassigned dynamically
ScalingMay require manual hardware changesCan use automated scaling
MonitoringMay be separated from provisioningMonitoring can directly trigger management actions
UtilizationMay leave excess capacity idleDesigned to match resources more closely to workload

Let's Clarify

A restaurant with fixed seating cannot immediately change capacity when hundreds of customers arrive. Dynamic cloud infrastructure behaves more like a system that can temporarily open additional service counters when demand rises and close them when demand falls. Monitoring detects the pressure, automation adds resources, and later automation releases unused capacity.

Summary

  • Cloud infrastructure combines data centers, servers, storage, networks, virtualization, management, and security systems.
  • Virtualization separates logical computing environments from physical hardware and supports flexible resource allocation.
  • Dynamic infrastructure uses monitoring, policies, and automation to adjust resources as workloads change.
  • A typical cycle is monitor → detect → provision → configure → use → measure → release or scale.
  • Orchestration coordinates several resource-management operations into repeatable workflows.
  • Dynamic resource allocation supports elasticity and improved infrastructure utilization.

Test Yourself

  1. Explain how monitoring and automation interact in dynamic cloud infrastructure.
  2. What are the challenges on cloud computing? Explain cloud services requirements and cloud infrastructure in detail. [3+4+3] (2026)

Hints:

  1. Monitoring collects workload metrics; policies evaluate those metrics; automation provisions, configures, scales, or releases resources according to the resulting decision.
  2. For cloud infrastructure, explain data centers, compute, storage, networking, virtualization, management/orchestration, and security resources.

1.10 Cloud adoption

Definition

Cloud adoption is the planned process through which an organization begins using cloud technologies, services, or infrastructure to support or replace existing information technology systems and business processes.


Cloud adoption is not the act of moving every application to an online server at once. Organizations first identify business needs, assess applications and data, choose suitable cloud models, plan migration, test the solution, move workloads, and then continuously govern and optimize the environment.

Detailed Explanation

An organization adopts cloud computing to achieve particular business or technical objectives. These may include faster deployment, flexible capacity, access to managed services, better geographic reach, modernization of older applications, improved recovery capability, or changes in infrastructure cost.

Because applications have different technical and business requirements, adoption should follow an organized roadmap rather than treating every workload identically.

Cloud Adoption Roadmap

Step 1: Define Business Objectives

The organization first establishes why cloud technology is being considered. Possible objectives include improving agility, reducing infrastructure-management effort, increasing scalability, improving recovery, supporting remote access, or enabling new digital services.

A migration has little value if the organization cannot connect it to a meaningful requirement.

Step 2: Assess Existing Environment

Existing applications, servers, databases, storage, networks, security controls, costs, dependencies, and staff capabilities are examined.

The assessment identifies:

  • which workloads are suitable for cloud migration;
  • which applications have technical dependencies;
  • which data is sensitive;
  • which systems have strict performance or availability requirements;
  • which workloads may need to remain in the existing environment.

Step 3: Evaluate Cloud Readiness and Requirements

The organization evaluates whether applications, data, network connectivity, security processes, operations teams, and governance practices are ready for cloud use.

The cloud service requirements discussed in 1.8 Cloud services requirements become part of this evaluation.

Step 4: Select Deployment and Service Models

The organization chooses appropriate deployment approaches such as public, private, community, or hybrid cloud and determines which workloads require IaaS, PaaS, SaaS, or a combination.

Step 5: Select Providers and Design Architecture

Provider capabilities are evaluated against technical, security, compliance, integration, cost, support, and availability requirements.

The target architecture defines how applications, networks, identities, storage, databases, monitoring, and security controls will operate after migration.

Step 6: Develop Migration Strategy

Different workloads may require different migration strategies. Common approaches include:

  • Rehost: move an application to cloud infrastructure with limited architectural change.
  • Replatform: move the workload while making selected changes to take advantage of cloud services.
  • Refactor: redesign or rewrite significant parts of an application to use cloud-native architecture or services.
  • Repurchase: replace an existing application with another product, often a SaaS solution.
  • Retain: keep a workload in its current environment for the time being.
  • Retire: remove a system that is no longer required.
StrategyMain Action
RehostMove with minimal architectural modification
ReplatformMove and make selected platform improvements
RefactorRedesign substantially for cloud capabilities
RepurchaseReplace with another product or service
RetainKeep the existing system
RetireDecommission an unnecessary system

Step 7: Conduct a Pilot or Proof of Concept

A limited workload can be migrated first to validate architecture, connectivity, security, performance, management procedures, and cost assumptions.

The pilot helps identify practical problems before a larger migration.

Step 8: Migrate Applications and Data

Applications, configurations, databases, and other data are moved according to the migration plan. Migration may occur in phases to reduce risk.

Testing should confirm that migrated systems operate correctly and that data remains complete and consistent.

Step 9: Secure and Govern the Cloud Environment

Cloud governance establishes policies and responsibilities for resource creation, identity management, security, data protection, cost control, naming, logging, compliance, and other operational activities.

Without governance, different teams can create inconsistent environments and uncontrolled resource consumption.

Step 10: Monitor and Optimize

After adoption, the organization monitors availability, performance, security events, resource usage, and cost.

Cloud adoption therefore continues after migration. Resources can be resized, architecture improved, unused services removed, and policies refined as requirements change.

Objectives → Assessment → Requirements → Cloud model → Architecture → Migration strategy → Pilot → Migration → Governance → Optimization

Organizational cloud adoption roadmap and migration stages

Factors Influencing Cloud Adoption

1. Business Factors

  • Business goals
  • Expected agility
  • Time required to deliver services
  • Growth plans
  • Competitive and customer requirements

2. Financial Factors

  • Existing infrastructure investment
  • Migration cost
  • Expected cloud consumption
  • Licensing cost
  • Training and operational cost
  • Network and data-transfer cost

3. Technical Factors

  • Application architecture
  • Dependencies between systems
  • Performance requirements
  • Network connectivity
  • Scalability needs
  • Integration requirements
  • Availability requirements

4. Security and Privacy Factors

  • Sensitivity of stored data
  • Identity and access requirements
  • Encryption requirements
  • Security monitoring
  • Provider security capabilities

5. Legal and Compliance Factors

  • Data-protection obligations
  • Audit requirements
  • Data-location requirements
  • Industry-specific regulations
  • Contractual obligations

6. Organizational Factors

  • Cloud skills of employees
  • Management support
  • Resistance to organizational change
  • Operational processes
  • Training requirements

7. Provider and Portability Factors

  • Provider reliability
  • Available cloud services
  • Technical support
  • Service-level commitments
  • Interoperability
  • Risk of vendor lock-in
  • Ease of moving applications and data

Cloud Adoption Strategy and Adoption Roadmap

A cloud adoption strategy describes the overall approach and decisions an organization will use when moving toward cloud computing. A cloud adoption roadmap converts that strategy into a sequence of practical activities and milestones.

ConceptMain Purpose
Cloud adoption strategyDefines why, where, and how the organization intends to use cloud technologies.
Cloud adoption roadmapDefines the ordered activities used to carry out the strategy.
Migration strategyDefines how a particular workload will move, change, remain, or be retired.
Cloud governanceDefines the rules and responsibilities for operating cloud resources after and during adoption.

Let's Clarify

Moving an entire college system to the cloud without assessment would be similar to shifting every department to a new building without checking room requirements, security needs, equipment, network access, or dependencies. A cloud adoption roadmap creates the sequence: understand what exists, define what is needed, decide what should move, test the approach, migrate carefully, and manage the resulting environment.

Common Mistake

Cloud adoption and cloud migration are not identical. Migration is the movement or transformation of particular workloads. Adoption is broader and includes business planning, architecture, skills, security, governance, provider selection, migration, and continuous optimization.

Summary

  • Cloud adoption is the planned organizational process of introducing cloud technologies and services.
  • A complete roadmap starts with business objectives and assessment before selecting architecture or moving workloads.
  • Workloads can follow different migration strategies such as rehost, replatform, refactor, repurchase, retain, and retire.
  • Business, financial, technical, security, compliance, organizational, and provider-related factors influence adoption decisions.
  • Governance defines how cloud resources, identities, security, compliance, and spending are controlled.
  • Adoption continues after migration through monitoring, optimization, and architectural improvement.

Test Yourself

  1. Differentiate cloud adoption, cloud migration, and cloud governance.
  2. What is cloud adoption? Explain the steps, strategies, and factors influencing cloud adoption in organizations. [1+4] (2026)
  3. Explain the key factors that organizations should consider before adopting cloud computing. (2025)
  4. Give a brief description of the organization's cloud adaptation roadmap. (2023)

Hints:

  1. Adoption is the overall organizational process; migration moves or transforms workloads; governance establishes rules and responsibilities for controlling the cloud environment.
  2. Define adoption, then explain objectives → assessment → requirements → model/provider selection → migration strategy → pilot → migration → governance → optimization. Include business, cost, technology, security, compliance, organizational, and provider factors.
  3. Cover business objectives, total cost, workload suitability, security/privacy, compliance, performance, connectivity, integration, skills, provider capability, portability, and vendor lock-in.
  4. Describe a phased roadmap: establish goals → assess current systems → define requirements → select cloud architecture and provider → plan migration → pilot → migrate → govern → monitor and optimize.

Exam Questions

  1. Describe the evolution of Cloud Computing with key technological developments that led to modern cloud computing. [5] (2026)
  2. What is cloud adoption? Explain the steps, strategies, and factors influencing cloud adoption in organizations. [1+4] (2026)
  3. What are the challenges on cloud computing? Explain cloud services requirements and cloud infrastructure in detail. [3+4+3] (2026)
  4. Explain the key factors that organizations should consider before adopting cloud computing. (2025)
  5. Explain on-demand resource Provisioning, Scalability and pay-as-you- go pricing model. (2024)
  6. What is bucket in Amazon simple storage service? How addressing of a bucket is done? (2024)
  7. Define cloud computing. (2024)
  8. Give a brief description of the organization's cloud adaptation roadmap. (2023)

Whole Chapter Summary

1.1 Overview of Cloud Computing

Cloud computing provides computing resources over a network rather than requiring every user or organization to own and operate all infrastructure locally. Its key value comes from flexible access to provider-managed computing, storage, networking, platforms, and software.

1.2 Evolution of Cloud Computing

Modern cloud computing developed from mainframes, time-sharing, computer networking, client-server computing, distributed and grid systems, virtualization, utility computing, web services, automation, and large-scale data centers.

1.3 Characteristics of Cloud Computing

Cloud computing is characterized by on-demand access, broad network availability, resource pooling, rapid elasticity, scalability, and measured consumption. These features allow infrastructure capacity to follow changing workload demand.

1.4 Types of cloud and its Cloud services

Public, private, community, and hybrid clouds describe deployment arrangements. IaaS, PaaS, and SaaS describe how much of the computing environment is managed by the provider and how much remains the customer's responsibility.

1.5 Benefits and challenges of cloud computing

Cloud computing can improve provisioning speed, scalability, accessibility, recovery options, and flexibility. Its challenges include security, privacy, network dependency, outages, cost control, compliance, migration complexity, vendor lock-in, and skill requirements.

1.6 Applications cloud computing

Cloud platforms are used for storage, websites, software delivery, education, collaboration, development, analytics, AI, disaster recovery, e-commerce, media delivery, and IoT systems.

1.7 Cloud Storage

Cloud storage provides remotely managed storage through object, block, or file models. Amazon S3 uses object storage, where buckets contain objects identified by object keys.

1.8 Cloud services requirements

A suitable cloud solution must satisfy requirements for availability, reliability, performance, scalability, security, privacy, compliance, interoperability, portability, manageability, recovery, networking, service levels, and cost.

1.9 cloud and dynamic infrastructure

Cloud infrastructure combines servers, storage, networks, virtualization, management, orchestration, security, and data-center facilities. Dynamic infrastructure uses monitoring and automation to provision, configure, scale, and release these resources according to demand.

1.10 Cloud adoption

Cloud adoption is an organizational process that begins with objectives and assessment, moves through architecture and migration planning, and continues through governance and optimization. Business, technical, financial, security, regulatory, organizational, and provider-related factors influence the process.

Key Formulas and Points Sheet

Formula / Rule / SequenceMeaning
Request → Provision → Resource availableBasic on-demand cloud resource provisioning flow.
Demand rises → Scale out/up → Demand falls → Scale in/downResource capacity follows workload demand.
Vertical scaling = change capacity of an existing machineAlso described as scaling up or down.
Horizontal scaling = change the number of machines or instancesAlso described as scaling out or in.
Measured consumption → Usage-based chargeBasic logic behind pay-as-you-go cloud pricing.
IaaS → PaaS → SaaSProvider management responsibility generally increases from infrastructure to complete software.
Public / Private / Community / HybridFour main cloud deployment models covered in the unit.
Object / Block / FileThree major cloud storage models.
https://bucket-name.s3.region-code.amazonaws.com/object-keyGeneral virtual-hosted-style Amazon S3 object-addressing pattern.
Monitor → Detect → Provision → Configure → Use → Measure → Scale or releaseDynamic cloud infrastructure management cycle.
Objectives → Assessment → Requirements → Cloud model → Architecture → Migration strategy → Pilot → Migration → Governance → OptimizationCloud adoption roadmap.
Rehost / Replatform / Refactor / Repurchase / Retain / RetireCommon workload strategies considered during cloud adoption.

Last-Minute Revision Sheet

ConceptTrigger PhraseRecall Cue
Cloud computingComputing as a network serviceServers + storage + network + software on demand
EvolutionShared computing became automated cloudMainframe → network → distributed → virtualization → utility → cloud
On-demand provisioningResources when requestedRequest → automatic allocation
Resource poolingShared provider capacityMany customers, pooled infrastructure
ScalabilityAbility to handle changing loadVertical + horizontal
ElasticityCapacity follows demandGrow when busy, shrink when quiet
Measured serviceConsumption recordedUsage metering
Pay-as-you-goCost follows consumptionUse → meter → charge
Public cloudProvider-operated shared cloudMultiple customers
Private cloudDedicated organizational cloudGreater direct control
Community cloudCloud for shared requirementsSeveral related organizations
Hybrid cloudCombination of cloudsPrivate + public capability
IaaSInfrastructure serviceVM + storage + network
PaaSApplication platformDeploy code, provider manages platform
SaaSFinished softwareUse application through network
Cloud benefitsFlexibility and rapid provisioningScale + access + managed resources
Cloud challengesRisk and dependencySecurity + outages + cost + compliance + lock-in
Cloud storageRemote provider-managed storageObject + block + file
S3 bucketObject containerBucket name + object key
Service requirementsWhat cloud must satisfyAvailability + performance + security + compliance + cost
Cloud infrastructureFoundation of cloud servicesCompute + storage + network + virtualization + management
Dynamic infrastructureAutomatic resource adjustmentMonitor → provision → scale → release
Cloud adoptionOrganizational move toward cloudAssess → plan → migrate → govern → optimize
RehostMove with little redesignMinimal architecture change
ReplatformMove with selected improvementsModerate platform change
RefactorRedesign for cloudMajor application change
RepurchaseReplace applicationOften move to SaaS
RetainKeep existing workloadNo migration yet
RetireRemove obsolete workloadDecommission
Views: …
TUpapers.com logo tupapers.com
  • Privacy Policy

  • Contact Us

  • Terms

  • Pricing

  • SEEpapers.com

TUpapers on Facebook
TUpapers on Instagram
Contact TUpapers on WhatsApp Contact TUpapers on WhatsApp
TUpapers subreddit on Reddit

Courses

  • BBA

  • BCA

  • BIT

  • CSIT

  • BBS

  • BHM

  • BBM

  • BITM

  • BTTM

  • BA

  • BE

  • BSW

© 2026 tupapers.com. All rights reserved.