CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Module II / Part I

Index

Topic: Standalone Applications

Topic: Traditional Web-Based Applications

Topic: Cloud-Based Applications

Topic: Comparison Table- Stand-Alone vs Web-Based vs Cloud-Based Applications

Topic: Cloud Management in Cloud Computing

Topic: Virtualization: The Foundation of Cloud Computing

Topic: Working of Virtualization (Basic)

 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Standalone Applications

1. Definition and Core Concept

A standalone application is a computer program designed to operate independently on a local computing
device without requiring continuous connection to external resources such as internet services, remote
servers, or networked databases. The application is self-contained and executes its primary functions using
the local device's hardware and software resources exclusively.

2. Key Characteristics
Operational Independence
 No requirement for active internet connectivity for core functionality
 No dependency on external server infrastructure for basic operations
 Self-sufficient in terms of computational resources and data processing
Installation and Deployment
 Requires installation directly onto the user's local storage medium
 Typically distributed via physical media or downloadable installation packages
 Contains all necessary libraries, frameworks, and runtime components within the installation bundle
Resource Utilization
 Operates exclusively using local hardware resources (processor, memory, storage)
 May integrate with local peripheral devices and hardware components
 Performance is determined by local system capabilities rather than network conditions
Data Management
 Stores and processes data locally on the device
 Utilizes local file systems or embedded database systems
 Data persistence is maintained within the device's storage architecture

3. Technical Architecture Components

Execution Environment
 Operates within the host operating system's process space
 Utilizes system APIs and services provided by the local OS
 May incorporate bundled runtime environments (Java Runtime, .NET Framework)
Component Structure
 Core executable files containing the primary application logic
 Supporting libraries and dependencies packaged with the application
 Configuration files and resources stored in local directories
 Local data storage mechanisms (files, embedded databases)
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Interaction Model
 User interface rendered locally using system graphical resources
 Input processing handled through local device interfaces
 Output generation managed entirely by local system components

4. Use Cases and Application Domains

Offline-Required Environments
 Field operations with unreliable or unavailable network connectivity
 Remote locations without internet infrastructure
 Secure facilities with network access restrictions
 Mobile deployments where connectivity cannot be guaranteed
Performance-Critical Applications
 Graphic-intensive processing (video editing, 3D rendering)
 Real-time data acquisition and processing systems
 Scientific computing and complex simulations
 High-performance gaming and interactive media
Specialized Hardware Integration
 Medical diagnostic and monitoring equipment
 Industrial control systems and automation software
 Laboratory instrumentation and data collection systems
 Embedded systems with proprietary hardware interfaces

5. Advantages
Performance and Reliability
 Consistent performance unaffected by network variability
 Reduced latency for time-sensitive operations
 Operational reliability independent of external service availability
 Optimized resource utilization through direct hardware access
Security and Privacy
 Reduced attack surface by eliminating network exposure
 Local data storage prevents unauthorized external access
 Simplified security model focusing on local protection mechanisms
 Compliance with data sovereignty requirements through localized processing
Cost and Operational Efficiency
 Predictable performance without bandwidth considerations
 No recurring costs for server infrastructure or cloud services
 Simplified operational model without dependency on service providers
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 Long-term usability independent of vendor service continuity

User Experience
 Consistent interface and performance characteristics
 Immediate responsiveness without network-induced delays
 Simplified user workflow without connectivity management concerns

6. Disadvantages and Limitations

Maintenance Challenges
 Updates and patches require manual distribution and installation
 Version management becomes complex across multiple installations
 Bug fixes and improvements cannot be deployed centrally
 Users may continue using outdated or vulnerable versions
Scalability Constraints
 Difficult to implement multi-user collaboration features
 Limited ability to share data or resources across installations
 Synchronization challenges for distributed deployments
 Resource constraints bounded by local hardware capabilities
Deployment and Management Overhead
 Installation required on each individual device
 Configuration management must be handled per installation
 License management requires individual tracking
 Support complexities due to varying system environments
Compatibility Issues
 Dependence on specific operating system versions and configurations
 Hardware compatibility requirements may limit deployment options
 Interoperability challenges with other systems and applications
 Platform-specific development and testing requirements
Feature Limitations
 Lack of real-time collaboration capabilities
 Limited access to cloud-based services and resources
 Reduced ability to leverage external computational resources
 Constrained data sharing and distribution mechanisms
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Traditional Web-Based Applications

1. Definition and Core Architecture

A traditional web-based application is a software application that operates on a centralized web server and
is delivered to users through a web browser interface over a network infrastructure, typically utilizing the
internet as its primary delivery mechanism. The application logic, data processing, and business operations
are executed primarily on the server side, with the client interface rendered within the browser
environment.

2. Fundamental Architecture Pattern (Client-Server Model)

Server-Side Components
 Web Server: Handles HTTP/HTTPS requests and serves static content (Apache, Nginx, IIS)
 Application Server: Executes business logic and processes dynamic content ([Link], Tomcat, .NET
Runtime)
 Database Server: Manages persistent data storage and retrieval (MySQL, PostgreSQL, MongoDB)
 Backend Processing: Server-side scripting languages (PHP, Python, Ruby, Java) that generate
dynamic responses
Client-Side Components
 Web Browser: Rendering engine for HTML, CSS, and JavaScript
 User Interface: HTML documents styled with CSS
 Client-Side Scripting: Limited JavaScript for interface interactions
 Stateless Interaction: Each request is independent (though sessions may maintain state)

3. Key Characteristics
Network Dependency
 Requires active internet or network connectivity for core functionality
 All application logic and data processing occurs on remote servers
 Client primarily serves as a presentation layer with limited processing capability
Centralized Architecture
 Single codebase deployed on central servers
 Uniform user experience across all access points
 Consolidated data storage and management
 Centralized security and access control implementation
Accessibility Parameters
 Platform-agnostic access through standards-compliant web browsers
 Geographic independence (accessible from any network-connected location)
 Device flexibility (compatible across desktops, laptops, tablets, smartphones)
 No local installation requirements beyond a compatible browser
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Deployment and Maintenance Model

 Updates deployed centrally on server infrastructure
 Instantaneous feature availability to all users
 Simplified version control and management
 Reduced client-side maintenance overhead

4. Technical Implementation Layers

Presentation Layer (Client Side)
 HTML for content structure and semantic markup
 CSS for visual styling and layout definition
 Basic JavaScript for user interface enhancements
 Limited client-side state management (cookies, local storage)
Business Logic Layer (Server Side)
 Server-side programming languages implementing core functionality
 Request processing and response generation
 Session management and user authentication
 Business rule validation and enforcement
Data Access Layer
 Database connectivity and query execution
 Data persistence and transaction management
 Data transformation and formatting
 Caching mechanisms for performance optimization
Communication Protocols
 HTTP/HTTPS for client-server communication
 Stateless request-response cycle
 Standardized status codes and methods
 Session management through cookies or tokens

5. Advantages and Benefits

Accessibility and Reach
 Universal access from any internet-connected device
 Elimination of platform-specific development requirements
 Reduced barriers to user adoption
 Support for geographically distributed user bases
Management and Maintenance Efficiency
 Centralized update deployment and version control
 Simplified bug fixing and patch management
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 Consistent user experience across deployments

 Reduced total cost of ownership through centralized management
Collaboration and Multi-User Support
 Real-time data sharing and collaboration capabilities
 Concurrent access by multiple users
 Centralized permission and access management
 Integrated communication and workflow features
Scalability and Performance Management
 Horizontal scalability through server clustering and load balancing
 Centralized performance monitoring and optimization
 Efficient resource utilization through shared infrastructure
 Elastic scaling to accommodate variable demand patterns
Security and Compliance
 Centralized security policy implementation
 Controlled data storage and backup management
 Simplified compliance auditing and reporting
 Reduced endpoint security vulnerabilities

6. Limitations and Challenges

Network Dependency
 Complete operational failure during network outages
 Performance degradation with poor connectivity
 Limited functionality in low-bandwidth environments
 Accessibility constraints in remote or restricted locations
Performance Considerations
 Latency introduced by network communication
 Server load impacts response times during peak usage
 Bandwidth consumption for data-intensive operations
 Limited offline functionality and operation
User Experience Constraints
 Interface limitations of browser environments
 Reduced responsiveness compared to native applications
 Inconsistent behavior across different browser implementations
 Limited access to device hardware and native features
Security Vulnerabilities
 Exposure to network-based attacks
 Dependence on browser security mechanisms
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 Cross-site scripting and injection attack vulnerabilities

 Session management and authentication challenges
Technical Limitations
 Browser compatibility and testing requirements
 Stateless nature requiring additional state management
 Limited client-side processing capabilities
 Restricted access to local system resources

7. Common Application Domains

Business and Enterprise Systems
 Customer Relationship Management (CRM) platforms
 Enterprise Resource Planning (ERP) systems
 Human Resource Management Systems (HRMS)
 Project management and collaboration tools
Financial Services
 Online banking and financial management
 Payment processing gateways
 Investment and trading platforms
 Accounting and bookkeeping systems
E-Commerce and Retail
 Online shopping platforms
 Inventory management systems
 Order processing and fulfillment
 Customer service portals
Education and Learning
 Learning Management Systems (LMS)
 Online course delivery platforms
 Student information systems
 Collaborative learning environments
Communication and Collaboration
 Email and messaging platforms
 Document sharing and collaboration tools
 Video conferencing applications
 Social networking platforms
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Cloud-Based Applications

1. Definition and Fundamental Architecture

A cloud-based application is a software system that operates on distributed cloud infrastructure rather than
local servers or individual devices. The application's execution, data storage, business logic, and user
interface delivery are all managed through remote cloud resources accessed via the internet. This represents
an evolution from traditional web applications through the utilization of cloud-native architectural patterns
and services.

2. Core Architectural Model

Cloud Infrastructure Components
 Virtualized Resources: Compute, storage, and networking provided as abstracted services
 Managed Services: Database, messaging, authentication, and other functions provided as APIs
 Orchestration Layer: Automated deployment, scaling, and management of application components
 Global Distribution: Content delivery networks and regional deployment for latency optimization
Application Delivery Model
 Multi-Tenant Architecture: Shared infrastructure serving multiple customers with logical isolation
 Service-Oriented Design: Applications composed of loosely coupled, independently scalable
services
 API-Centric Communication: Internal and external interfaces exposed as well-defined APIs
 Stateless Design: Application components designed without persistent local state for horizontal
scalability

3. Essential Characteristics
Resource Abstraction and Virtualization
 Applications consume infrastructure as services rather than physical hardware
 Dynamic resource allocation based on demand patterns
 Geographic independence of infrastructure concerns
 Automatic failover and redundancy mechanisms
On-Demand Self-Service
 Users can provision resources without human intervention from providers
 Automated scaling based on predefined metrics and thresholds
 Self-service management interfaces and APIs
 Real-time resource adjustment capabilities
Elastic Scalability
 Automatic horizontal scaling based on load metrics
 Resource pooling across multiple users and applications
 Pay-per-use resource consumption model
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 Near-infinite theoretical scalability limits

Measured Service
 Granular monitoring of resource consumption
 Transparent billing based on actual usage
 Performance metrics and analytics
 Cost optimization through usage analysis

4. Deployment Models
Public Cloud Deployment
 Infrastructure owned and operated by third-party providers
 Maximum scalability and cost efficiency
 Shared responsibility security model
 Examples: AWS, Azure, Google Cloud Platform
Private Cloud Deployment
 Dedicated infrastructure for single organization
 Enhanced control and customization
 Higher security and compliance capabilities
 Greater capital expenditure requirements
Hybrid Cloud Deployment
 Integration of public and private cloud environments
 Workload placement based on requirements
 Data and application portability between environments
 Complex management and integration requirements
Multi-Cloud Deployment
 Utilization of services from multiple cloud providers
 Reduced vendor lock-in risks
 Best-of-breed service selection
 Increased management complexity

5. Service Models for Cloud Applications

Infrastructure as a Service (IaaS)
 Fundamental computing resources provisioned as services
 User manages applications, data, runtime, middleware, OS
 Provider manages virtualization, servers, storage, networking
 Examples: AWS EC2, Azure Virtual Machines, Google Compute Engine
Platform as a Service (PaaS)
 Complete development and deployment environment in cloud
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 User manages applications and data only

 Provider manages runtime, middleware, OS, virtualization, servers, storage, networking
 Examples: Heroku, Google App Engine, Microsoft Azure App Service
Software as a Service (SaaS)
 Complete software applications delivered over internet
 User only manages limited application-specific configurations
 Provider manages everything from application to infrastructure
 Examples: Salesforce, Google Workspace, Microsoft 365
Function as a Service (FaaS)
 Event-driven execution of code without server management
 Pure business logic execution in stateless containers
 Automatic scaling and high availability
 Examples: AWS Lambda, Azure Functions, Google Cloud Functions

6. Key Advantages
Economic Benefits
 Capital Expenditure Reduction: Conversion to operational expenditure
 Pay-Per-Use Model: Costs aligned with actual consumption
 Economies of Scale: Provider efficiencies passed to customers
 Reduced Maintenance Costs: Automated updates and management
Operational Efficiency
 Rapid Deployment: Minutes instead of weeks for provisioning
 Automated Management: Self-healing and auto-scaling capabilities
 Global Reach: Deployment across multiple geographic regions
 High Availability: Built-in redundancy and failover mechanisms
Scalability and Performance
 Elastic Resources: Dynamic adjustment to demand patterns
 Performance Optimization: Geographic distribution reducing latency
 Load Distribution: Intelligent traffic routing and balancing
 Resource Optimization: Right-sizing based on actual requirements
Innovation and Agility
 Rapid Prototyping: Quick experimentation with new features
 Service Integration: Easy incorporation of advanced cloud services
 Continuous Deployment: Automated testing and release pipelines
 Technology Adoption: Access to latest innovations without upfront investment
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

7. Limitations and Challenges

Security and Privacy Concerns
 Data Sovereignty: Legal jurisdiction over geographically distributed data
 Shared Responsibility Model: Confusion over security boundaries
 Multi-Tenancy Risks: Potential isolation failures between customers
 Compliance Challenges: Meeting industry-specific regulatory requirements
Control and Customization Limitations
 Limited Infrastructure Control: Dependence on provider capabilities and SLAs
 Vendor Lock-in: Proprietary services and APIs creating migration barriers
 Configuration Constraints: Limited ability to customize underlying infrastructure
 Transparency Issues: Limited visibility into provider operations and incident management
Technical Challenges
 Latency Sensitivity: Performance impact for real-time applications
 Data Transfer Costs: Expenses associated with moving large datasets
 Integration Complexity: Connecting cloud and on-premises systems
 Skill Requirements: Need for specialized cloud expertise
Operational Risks
 Provider Dependency: Business continuity tied to provider viability
 Internet Dependency: Complete reliance on network connectivity
 Service Outages: Impact of provider-wide service disruptions
 Cost Management Complexity: Unpredictable expenses without careful monitoring

8. Technical Implementation Patterns

Microservices Architecture
 Decomposition into small, independently deployable services
 API-based communication between services
 Independent scaling of individual components
 Technology diversity across service boundaries
Containerization
 Package applications with dependencies into standardized units
 Consistent runtime environment across development and production
 Efficient resource utilization through lightweight isolation
 Orchestration for automated deployment and management
Serverless Computing
 Event-driven execution without server provisioning
 Automatic scaling from zero to high concurrency
 Fine-grained billing based on execution time and resources
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

 Reduced operational overhead

Event-Driven Architecture
 Loose coupling through asynchronous messaging
 Event sourcing for state management
 Reactive systems responding to events in real-time
 Improved resilience through message queuing

9. Security Architecture
Shared Responsibility Model
 Provider Responsibility: Security of the cloud infrastructure
 Customer Responsibility: Security in the cloud (applications, data, configurations)
 Varies by Service Model: Different boundaries for IaaS, PaaS, and SaaS
Identity and Access Management
 Centralized authentication and authorization
 Role-based access control with least privilege principles
 Multi-factor authentication enforcement
 Regular access review and auditing
Data Protection
 Encryption at rest and in transit
 Key management best practices
 Data classification and handling policies
 Secure data deletion and disposal procedures
Network Security
 Virtual private cloud isolation
 Security group and firewall configuration
 DDoS protection services
 Network monitoring and intrusion detection
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

10. Industry Applications and Examples

Enterprise Applications
 CRM: Salesforce, HubSpot
 ERP: SAP S/4HANA Cloud, Oracle Cloud ERP
 Collaboration: Microsoft Teams, Slack
 Productivity: Google Workspace, Microsoft 365
Consumer Services
 Streaming: Netflix, Spotify
 Storage: Dropbox, Google Drive
 Social Media: Facebook, Twitter
 E-commerce: Shopify, Amazon
Industry-Specific Solutions
 Healthcare: Electronic Health Record systems
 Finance: Banking and trading platforms
 Education: Learning management systems
 Manufacturing: Supply chain and logistics platforms
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Comparison Table- Stand-Alone vs Web-Based vs Cloud-Based Applications

Feature Stand-Alone Application Web-Based Application Cloud-Based

Application
Definition Software that runs Application accessed Application that runs
completely on a local through web browser on cloud infrastructure
computer without needing that runs on a web server and uses cloud services
internet or server
Internet No Yes Yes
Required
Installation Yes (on each device) No (just browser) No (just browser or
Needed lightweight client)
Where Data Local computer only Central server/database Cloud servers
Stored (distributed)
Where Local computer Web server Cloud servers
Processing
Happens
Accessibility Only on installed device Anywhere with internet Anywhere with internet
Updates Manual installation on each Automatic (server-side Automatic (managed
device only) by provider)
Cost Model One-time purchase/license Server hosting + Pay-as-you-go
maintenance fees subscription
Scalability Fixed (limited by local Limited (server capacity) High (auto-scales with
hardware) demand)
Multi-User Usually single-user Yes, but limited by Yes, with high
Access server concurrency
Maintenance User responsibility Organization's IT team Cloud provider's
responsibility
Backup Manual user backup Server backups needed Automatic cloud
backups
Security Local security only Server + network Advanced cloud
security security + compliance
Performance Fast (no network delay) Depends on server load Consistent (optimized
& internet resources)
Examples MS Word (offline), College website, Online Netflix, Google D
Photoshop, PC Games banking portal
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Cloud Management in Cloud Computing

Cloud Management is the process of administering, monitoring, controlling, and optimizing cloud
computing resources and services. It involves using specialized tools and practices to manage cloud
infrastructure, platforms, and applications to ensure efficiency, security, compliance, and cost-effectiveness.
Analogy to Understand:
 Database = Cloud (The resource/storage itself)
 DBMS = Cloud Management (The system that manages the resource)
 Just as DBMS manages databases without users touching raw data files, Cloud Management
systems manage cloud resources without users touching physical servers.

As more businesses shift to cloud platforms, managing cloud services has become crucial. Cloud
management involves monitoring and controlling cloud resources like storage, computing power, and
applications, across public, private, or hybrid environments. It ensures everything runs smoothly, securely,
and efficiently while meeting the growing demands of modern organizations.

1. What is Cloud Management

Cloud computing management is maintaining and controlling the cloud services and resources be it
public, private or hybrid. Some of its aspects include load balancing, performance, storage, backups,
capacity, deployment etc. To do so a cloud managing personnel needs full access to all the functionality of
resources in the cloud. Different software products and technologies are combined to provide a cohesive
cloud management strategy and process.
As we know Private cloud infrastructure is operated only for a single organization, so that can be managed
by the organization or by a third party. Public cloud services are delivered over a network that is open and
available for public use. In this model, the IT infrastructure is owned by a private company and members of
the public can purchase or lease data storage or computing capacity as needed. Hybrid cloud environments
are a combination of public and private cloud services from different providers. Most organizations store
data on private cloud servers for privacy concerns, while leveraging public cloud applications at a lower
price point for less sensitive information. The combination of both the public and private cloud are known
as Hybrid cloud servers.

2. Why Cloud Management

Cloud is nowadays preferred by huge organizations as their primary data storage. A small downtime or an
error can cause a great deal of loss and inconvenience for the organizations. So as to design, handle and
maintain a cloud computing service specific members are responsible who make sure things work out as
supposed and all arising issues are addressed.
3. Cloud Management Platform
A cloud management platform is a software solution that has a robust and extensive set of APIs that allow
it to pull data from every corner of the IT infrastructure. A CMP allows an IT organization to establish a
structured approach to security and IT governance that can be implemented across the organization's entire
cloud environment.
4. Cloud Management Tasks
The below figure represents different cloud management tasks :
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Cloud Management Tasks

 Auditing System Backups -
It is required to audit the backups from time to time to ensure restoration of randomly selected files
of different users. This might be done by the organization or by the cloud provider.
 Flow of data in the system -
The managers are responsible for designing a data flow diagram that shows how the data is supposed
to flow throughout the organization.
 Vendor Lock-In -
The managers should know how to move their data from a server to another in case the organization
decides to switch providers.
 Knowing provider’s security procedures -
The managers should know the security plans of the provider, especially Multitenant use, E-
commerce processing, Employee screening and Encryption policy.
 Monitoring the Capacity, Planning and Scaling abilities -
The manager should know if their current cloud provider is going to meet their organization’s
demand in the future and also their scaling capabilities.
 Monitoring audit log -
In order to identify errors in the system, logs are audited by the managers on a regular basis.
 Solution Testing and Validation -
It is necessary to test the cloud services and verify the results and for error-free solutions.
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

5. Benefits of Effective Cloud Management

Managing the cloud effectively brings several advantages that help organizations run smoothly and save
money:
 Cost Optimization: Helps avoid unnecessary spending by tracking and controlling how cloud
resources are used.
 Better Security & Compliance: Ensures sensitive data is protected and meets legal or industry-
specific rules.
 High Performance & Uptime: Keeps systems running fast and reduces downtime, which is crucial
for customer satisfaction.
 Clear Usage Insights: Offers full visibility into what’s being used, by whom, and how much it costs.
 Quick Problem Detection: Makes it easier to spot and fix issues before they cause major
disruptions.

6. Key Features of a Good Cloud Management Platform

A good Cloud Management Platform (CMP) makes it easier to handle cloud resources efficiently. Here’s
what to look for:
 Multi-cloud & Hybrid Support: Works across different cloud providers (like AWS, Azure, GCP)
and setups (private + public).
 Unified Dashboard: Shows everything in one place, usage, health, performance, so it’s easier to
manage.
 Automation Tools: Saves time by automating tasks like scaling, backups, and updates.
 Cost Tracking: Helps monitor spending and predict future cloud costs to avoid budget surprises.
 DevOps Integration: Works well with tools like CI/CD, Terraform, etc., for smoother deployments
and updates.
7. Security and Compliance in Cloud Management
Identity and Access Management (IAM)
It ensures that only the right people have access to the right resources. It helps control who can view or
change what in the cloud, reducing the chances of data leaks or unauthorized access.
Encryption at rest and in transit
It means the data is scrambled so no one can read it—whether it's stored in the cloud or being sent from
one place to another. This keeps sensitive information safe from hackers or breaches.
Cloud Security Posture Management (CSPM)
It is like a security health check for the cloud. It continuously monitors for risks, misconfigurations, or
weak spots, and alerts you before any real damage happens.
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Virtualization: The Foundation of Cloud Computing (Only Basic Concept, Details Will be in
Module 3)

[Link] Concept
Definition: Virtualization is a technology that creates abstract, virtual versions of physical computing
resources (servers, storage, networks, operating systems), allowing multiple virtual environments to run
simultaneously on a single physical machine.
Simple Analogy: Think of an apartment building:
 Physical Building = One physical server
 Individual Apartments = Multiple virtual machines
 Each apartment has its own kitchen, bathroom, living space (like each VM has its own OS, apps,
storage)
 But all apartments share the building's foundation, structure, and utilities (like VMs share physical
hardware)

2. The Problem Before Virtualization

Scenario: Without Virtualization
 One Physical Server: 1 TB storage, 16 CPU cores, 64 GB RAM
 Single Operating System: Windows Server or Linux installed directly
 Single Application: Maybe just a database or web server running
 Resource Wastage:
o Application uses only 100 GB storage → 900 GB unused
o Uses only 4 CPU cores → 12 cores idle
o Uses only 8 GB RAM → 56 GB wasted
 Result: Expensive hardware mostly sitting idle
Real-World Impact:
 Low Utilization: Typical server utilization: 5-15%
 High Costs: Buying multiple servers for different applications
 Energy Waste: All servers drawing full power regardless of usage
 Space Consumption: Large data centers with mostly idle hardware

3. Virtualization Solution
Scenario: With Virtualization
Same Physical Server: 1 TB storage, 16 CPU cores, 64 GB RAM
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

After Virtualization:
Physical Server (1 machine)
↓
Virtualization Layer (Hypervisor)
↓
Virtual Machine 1: 200 GB, 4 cores, 8 GB RAM → Runs Web Server (Linux)
Virtual Machine 2: 300 GB, 4 cores, 16 GB RAM → Runs Database (Windows)
Virtual Machine 3: 250 GB, 4 cores, 12 GB RAM → Runs Application Server
Virtual Machine 4: 250 GB, 4 cores, 8 GB RAM → Runs Backup Server
Remaining: 20 GB free for future needs

Key Improvement:
 Utilization: From 15% to 85-90%
 Cost: One server doing work of four
 Flexibility: Different OSes on same hardware
 Isolation: Problems in one VM don't affect others
 CSE 336 CLOUD COMPUTING

Module – II / Part - I By Bikram Roy

Topic: Working of Virtualization (Basic)

Virtualization is a technology that allows multiple virtual computers, called Virtual Machines (VMs), to
run on a single physical computer using special software known as a hypervisor.
How It Works:
 Virtualization uses a hypervisor to divide the resources of a physical machine into multiple isolated
virtual environments.
 After installing virtualization software, users can create one or more virtual machines on the same
physical system.
 Each virtual machine behaves like a real, independent computer, even though it shares the same
physical hardware.
Key Concepts:
 The physical computer is called the Host machine.
 The virtual computers running on it are called Guest machines.
 A single host can run multiple guest virtual machines simultaneously.
 Each guest VM can have its own operating system, which may be the same as or different from the
host OS.
 Virtual machines operate like regular applications on the host system.
 Every VM has its own:
o Operating system
o Software and applications
o Configuration and settings
Resource Utilization:
 Virtual machines share physical resources such as:
o CPU
o RAM
o Storage
 The hypervisor manages these resources and ensures that each VM functions as if it has its own
dedicated hardware, while maintaining isolation between VMs.
Result:
Virtualization improves hardware utilization, enables efficient resource management, and allows
multiple operating systems to run securely on a single physical machine.