0% found this document useful (0 votes)
3 views

Cloud Computing

The document compares on-premise data centers and cloud computing, highlighting differences in ownership, cost structure, scalability, maintenance, security, and accessibility. It also differentiates between Amazon Web Services and Microsoft Azure, discusses the NIST definition of cloud computing, and describes Google App Engine's components and services. Additionally, it traces the evolution of cloud computing, analyzes cloud referencing models in healthcare, and examines various types of hypervisors and virtualizations.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views

Cloud Computing

The document compares on-premise data centers and cloud computing, highlighting differences in ownership, cost structure, scalability, maintenance, security, and accessibility. It also differentiates between Amazon Web Services and Microsoft Azure, discusses the NIST definition of cloud computing, and describes Google App Engine's components and services. Additionally, it traces the evolution of cloud computing, analyzes cloud referencing models in healthcare, and examines various types of hypervisors and virtualizations.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

1 : Compare and contrast the difference between on premise data center and

cloud computing.

1. Ownership:

On-Premise Data Center:Organization owns and manages the entire infrastructure


(servers, storage, network equipment).

Cloud Computing:Third-party provider owns and manages the infrastructure; users


access it remotely.

2. Cost Structure:

On-Premise Data Center: 1.High upfront costs (capital expenditure) for hardware,
software, and facilities. 2.Ongoing costs for maintenance, power, and upgrades.

Cloud Computing: 1.Pay-as-you-go or subscription-based pricing (operational


expenditure). 2.No upfront hardware costs; pay only for what you use.

3. Scalability:

On-Premise Data Center: 1.Scaling requires purchasing and installing additional


hardware. 2.Limited flexibility and longer setup times.

Cloud Computing: 1.Easily scalable with instant resource allocation. 2.Can scale up or
down based on demand.

4. Maintenance:

On-Premise Data Center: 1.Organization is responsible for all maintenance (hardware,


software, security, and upgrades).

Cloud Computing: 1.Provider handles all maintenance (hardware, software, security


updates, and upgrades).

5. Security:

On-Premise Data Center: 1. Full control over physical and network security measures.
2.Responsibility for securing the entire infrastructure.

Cloud Computing: 1.Security managed by the cloud provider, though the user still
shares responsibility (data encryption, access control). 2.Security features like
firewalls, encryption, and multi-factor authentication are provided.

6. Accessibility:

On-Premise Data Center: 1.Limited access; typically requires on-site or remote VPN
access. 2.Harder for remote work setups.

Cloud Computing: 1.Accessible from anywhere with an internet connection.


2: Differentiate between Amazon web services and Microsoft Azure.
1. Service Provider:

• AWS: Provided by Amazon, launched in 2006.

• Azure: Provided by Microsoft, launched in 2010.

2. Market Share:

• AWS: Holds the largest share of the global cloud market.

• Azure: Second-largest cloud provider, growing rapidly, especially in hybrid cloud


solutions.

3. Service Range:

• AWS: Offers a broad range of services, including compute, storage, AI, IoT, and
machine learning.

• Azure: Provides similar services but with stronger emphasis on hybrid cloud and
integration with Microsoft products (e.g., Windows Server, SQL Server).

4. Pricing Model:

• AWS: Pay-as-you-go model with charges based on usage. Pricing can be


complex.

• Azure: Also pay-as-you-go, with specific discounts for businesses using


Microsoft products (e.g., Microsoft 365 or SQL Server).

5. Hybrid Cloud:

• AWS: Offers hybrid solutions like AWS Outposts, but its focus is more on public
cloud.

• Azure: Stronger in hybrid cloud, with tools like Azure Stack and Azure Arc to
bridge on-premise and cloud environments.

6. Integration with Existing Infrastructure:

• AWS: Ideal for businesses needing flexibility and open-source tools, not tied to
Microsoft products.

• Azure: Seamlessly integrates with Microsoft-based infrastructure and services,


making it ideal for enterprises using Windows and Office 365.
3: Describe the NIST definition of cloud computing and briefly illustrate the
advantages and disadvantages of cloud computing from a real-time perspective.

The National Institute of Standards and Technology (NIST) defines cloud computing as:

"A model for enabling ubiquitous, convenient, on-demand network access to a shared
pool of configurable computing resources (e.g., networks, servers, storage,
applications, and services) that can be rapidly provisioned and released with minimal
management effort or service provider interaction."

NIST outlines five essential characteristics of cloud computing:

1. On-demand self-service: Users can provision and manage computing resources


without requiring human interaction with the service provider.

2. Broad network access: Cloud services are available over the network, accessible
from various devices (e.g., laptops, smartphones).

3. Resource pooling: Cloud providers pool resources to serve multiple customers,


dynamically allocating resources based on demand.

4. Rapid elasticity: Resources can be rapidly scaled up or down to meet fluctuating


demand.

5. Measured service: Cloud services are metered, and users pay only for the
resources they consume.

Advantages of Cloud Computing:

1. Cost Efficiency:

o Real-time Perspective: Companies don’t have to invest in costly physical


infrastructure (servers, storage).

2. Scalability and Flexibility:

o Real-time Perspective: Cloud resources can be quickly scaled up or down


based on business needs.

Disadvantages of Cloud Computing:

1. Downtime and Reliability Issues:Real-time Perspective: Cloud services are


dependent on internet connectivity.

2. Security Concerns:

o Real-time Perspective: Although cloud providers implement high levels of


security, there is still a concern over data privacy, especially if sensitive
data is stored on external servers.
4: Discuss the working of Google App Engine along with their components and
services

Working of Google App Engine (GAE):

Google App Engine (GAE) is a Platform-as-a-Service (PaaS) that allows developers to


build and deploy web applications without managing the underlying infrastructure. It
automates the scaling, load balancing, and management of applications. Developers
simply write their code, upload it to GAE, and the platform handles deployment, traffic
management, and resource scaling automatically.

Components of Google App Engine:

1. App Engine Standard Environment: 1.Provides predefined runtime environments


(e.g., Python, Java, Go). 2.Offers automatic scaling and is ideal for simple
applications with minimal configuration.

2. App Engine Flexible Environment: 1. Supports custom runtimes, offering more


control over the environment (using Docker containers). 2.Ideal for complex
applications that need specific libraries or dependencies.

3. App Engine Services:Allows you to break your application into separate services
(e.g., front-end, back-end, user authentication) that can scale independently.

Key Services:

1. Automatic Scaling:

o GAE automatically adjusts the number of instances running based on


demand, ensuring optimal resource utilization.

2. Google Cloud Datastore & Cloud SQL:

o Datastore is a NoSQL database, while Cloud SQL provides managed


relational databases (MySQL, PostgreSQL).

3. Cloud Storage:

o Provides scalable storage for large files like images and videos.

4. Task Queues:

o Allows for asynchronous background processing of tasks, such as


sending emails or handling long-running operations.

5. Logging & Monitoring:

o Integrated with Cloud Monitoring and Cloud Logging for real-time insights
into application performance.
5. Trace the evolution of cloud computing from traditional computing models to
modern cloud architectures.

Evolution of Cloud Computing:

1. Traditional Computing (Pre-Cloud Era):

o In the early days, businesses relied on on-premise infrastructure—


physical servers, data centers, and hardware—managed and maintained
internally. Scaling resources required heavy investments in hardware and
IT personnel. This model was costly, rigid, and required long deployment
times.

2. Virtualization (Early 2000s):

o The advent of virtualization technologies (like VMware) allowed for


multiple virtual machines (VMs) to run on a single physical server. This
improved resource utilization, reduced costs, and enabled easier
management of IT resources but still required businesses to own and
maintain infrastructure.

3. Introduction of Cloud Computing (Mid-2000s):

o Amazon Web Services (AWS) launched in 2006, marking the birth of


public cloud computing. It offered Infrastructure-as-a-Service (IaaS),
allowing users to rent virtualized computing resources (compute, storage,
networking) without maintaining physical hardware. This on-demand
model reduced upfront costs and allowed for scalable, flexible services.

4. Rise of Platform and Software as a Service (2008-2010):

o As cloud adoption grew, companies like Google and Microsoft introduced


Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS) models,
allowing businesses to focus on building applications and using software
without worrying about infrastructure. Examples include Google App
Engine and Microsoft Azure. This phase also saw the rise of cloud-based
office tools like Google Docs and Salesforce.

5. Modern Cloud Architectures (2010-Present):

o Cloud computing has evolved into hybrid cloud, multi-cloud, and


serverless architectures, enabling organizations to combine on-premises,
private cloud, and public cloud solutions. Microservices, containerization
(using tools like Docker and Kubernetes), and serverless computing (e.g.,
AWS Lambda) have revolutionized cloud application architectures,
offering extreme flexibility, scalability, and efficiency.
6: Analyze various cloud referencing models and its application to healthcare
systems

Cloud Referencing Models in Healthcare Systems:

Cloud computing models, such as Infrastructure-as-a-Service (IaaS), Platform-as-a-


Service (PaaS), and Software-as-a-Service (SaaS), are transforming healthcare systems
by enabling scalable, flexible, and cost-effective solutions. These models are tailored to
meet the diverse needs of healthcare organizations.

1. IaaS (Infrastructure-as-a-Service):

• Definition: IaaS provides virtualized computing resources like storage,


networking, and processing power over the cloud.

• Application in Healthcare: Healthcare providers can store large amounts of


patient data, medical records, and imaging files securely without investing in
expensive on-premise infrastructure.

2. PaaS (Platform-as-a-Service):

• Definition: PaaS offers a platform allowing developers to build and deploy


applications without managing the underlying infrastructure.

• Application in Healthcare: Developers can create healthcare applications for


patient management systems, telemedicine platforms, and health analytics
tools.

3. SaaS (Software-as-a-Service):

• Definition: SaaS delivers software applications over the internet on a


subscription basis.

• Application in Healthcare: Electronic Health Records (EHR) and Electronic


Medical Records (EMR) systems can be delivered via SaaS, allowing doctors and
medical professionals to access patient data from any device, improving
efficiency.

4. Hybrid Cloud Model:

• Definition: Combines private and public cloud infrastructure, allowing data and
applications to move between the two.

• Application in Healthcare: Private clouds store sensitive patient data to ensure


compliance with regulations like HIPAA and GDPR, while public clouds handle
less sensitive workloads such as data analytics or administrative tasks.
7: Differentiate between Type 1 and Type 2 hypervisors with examples.
Difference Between Type 1 and Type 2 Hypervisors:

1. Definition:

o Type 1 Hypervisor: Also known as bare-metal hypervisor, it runs directly


on the host hardware and does not require an underlying operating
system. It manages the hardware resources and controls guest virtual
machines (VMs).

o Type 2 Hypervisor: Known as a hosted hypervisor, it runs on top of an


existing operating system and relies on the host OS for resource
management and hardware access.

2. Performance:

o Type 1 Hypervisor: Offers better performance and efficiency since it


interacts directly with hardware without the overhead of a host OS.

o Type 2 Hypervisor: Performance is generally slower because it depends


on the host operating system to manage hardware resources, leading to
higher overhead.

3. Examples:

o Type 1 Hypervisor: 1. VMware vSphere/ESXi 2. Microsoft Hyper-V 3. Xen

o Type 2 Hypervisor: 1. VMware Workstation 2. Oracle VirtualBox

o 3. Parallels Desktop

4. Use Case:

o Type 1 Hypervisor: Primarily used in data centers, cloud environments,


and enterprise-level virtualizations where performance and resource
efficiency are critical.

o Type 2 Hypervisor: Often used for personal virtualization, development


environments, and testing on desktops or laptops.

5. Security:

o Type 1 Hypervisor: Generally considered more secure due to its direct


access to hardware and minimal dependency on external software layers
(no host OS).

o Type 2 Hypervisor: More vulnerable because it is dependent on the host


OS for security, which can introduce additional risks.
8: Compare and contrast at least any three today’s hypervisors.
Comparison of Three Popular Hypervisors: VMware ESXi, Microsoft Hyper-V, and Oracle
VirtualBox

1. VMware ESXi (Type 1 Hypervisor):

o Features: Known for its enterprise-grade performance and features like


vMotion (live migration of VMs), DRS (Distributed Resource Scheduler),
and HA (High Availability).

o Use Case: Primarily used in large data centers and enterprise


environments for high-performance, mission-critical workloads.

o Management: Managed through the vSphere Client or vCenter Server for


centralized control over multiple ESXi hosts.

o Cost: Expensive, with licensing fees for advanced features.

2. Microsoft Hyper-V (Type 1 Hypervisor):

o Features: Includes features such as Live Migration, Dynamic Memory,


Replica for disaster recovery, and integration with Windows Admin Center
for management.

o Use Case: Ideal for organizations using Windows environments and


looking for easy integration with other Microsoft products like Active
Directory and System Center.

o Management: Managed through the Hyper-V Manager or System Center


Virtual Machine Manager.

o Cost: More affordable for organizations already using Windows Server or


for small-scale virtual environments.

3. Oracle VirtualBox (Type 2 Hypervisor):

o Features: Supports various guest OSes, has features like snapshot


management, shared folders for file exchange, and remote desktop
access to VMs.

o Use Case: Primarily used for desktop virtualization, development, and


testing purposes. Suitable for users who want to run multiple OSes on a
single machine.

o Management: Managed via a GUI or command-line interface.

o Cost: Free and open-source, making it a popular choice for personal,


academic, or development use.
9: Examine various types of virtualizations with a neat sketch
Types of Virtualization

Virtualization technology enables the creation of multiple virtual instances of


resources, such as servers, storage, or networks, on a single physical machine. The
primary types of virtualization include:

1. Hardware Virtualization (Server Virtualization)

• This is the most common type of virtualization, where virtual machines (VMs) run
on a physical server. Each VM can have its own operating system and
applications, isolated from the others.

2. Storage Virtualization

• Storage virtualization combines multiple physical storage devices into a single


virtualized storage pool. This makes storage management easier and more
flexible.

3. Network Virtualization

• Network virtualization combines multiple physical networks into a single,


virtualized network. It allows for the creation of virtual networks (subnets) that
are independent of the physical hardware.

4. Desktop Virtualization

• Desktop virtualization allows users to run a desktop operating system (like


Windows) on a virtual machine, which is often hosted on a server. The user
interacts with the virtual desktop remotely through a thin client or a web browser.

5. Application Virtualization

• Application virtualization allows applications to run on a host machine without


being installed on it. The application is executed from a virtualized environment,
and the OS only interacts with the application through a virtual layer.

• Operating system virtualization, also known as containerization, involves running


multiple isolated user-space instances (containers) on a single OS kernel.

• Containers are lightweight, faster, and more efficient than traditional


virtualization because they share the host OS kernel.
10: Determine the significance of hypervisors and its application in cloud
computing environment.

1. Efficient Resource Utilization

Hypervisors allow multiple virtual machines (VMs) to run on a single physical machine,
optimizing the use of hardware resources like CPU, memory, and storage.

2. Isolation and Security

Hypervisors provide resource isolation between VMs, ensuring that each VM operates
independently without interfering with others. This isolation enhances security by
preventing one VM from accessing or damaging the resources or data of another VM.

3. Scalability and Flexibility

Hypervisors enable on-demand scalability by allowing VMs to be quickly created,


cloned, or removed depending on workload requirements. In cloud environments, this
elasticity is essential for handling fluctuating demand efficiently.

4. Cost Efficiency

Hypervisors help reduce operational costs by allowing multiple virtualized workloads to


run on fewer physical machines. This reduces the number of servers required in a data
center, resulting in savings on hardware, power consumption, cooling, and
maintenance.

5. Multi-Tenancy and Cloud Resource Management

Hypervisors facilitate multi-tenancy by enabling different organizations or users to


share the same physical infrastructure while keeping their virtual environments
isolated. This is especially important for public cloud providers who offer shared
resources to multiple customers.

6. Live Migration and High Availability

Hypervisors support live migration, enabling virtual machines to be moved between


physical hosts without shutting them down. This capability is essential in cloud
environments for load balancing, maintenance, and disaster recovery.

Application in Cloud Computing

Hypervisors are integral to IaaS (Infrastructure as a Service) models in cloud


computing. They enable cloud platforms such as Amazon EC2, Microsoft Azure Virtual
Machines, and Google Compute Engine to deliver virtualized computing resources to
customers.
11 : Demonstrate virtualization software operation with a neat diagram.
Virtualization software, also known as a hypervisor, is the key component in
virtualization technology. It allows a single physical server to run multiple virtual
machines (VMs), each with its own operating system (OS), applications, and resources,
isolated from one another.

Key Components of Virtualization Software:

1. Physical Hardware: The underlying physical machine providing CPU, memory,


storage, and network resources.

2. Hypervisor: Software that abstracts and allocates the physical resources to


virtual machines. There are two types of hypervisors:

o Type 1 (Bare-metal Hypervisor): Installed directly on physical hardware


(e.g., VMware ESXi, Microsoft Hyper-V).

o Type 2 (Hosted Hypervisor): Runs on top of a host OS (e.g., VirtualBox,


VMware Workstation).

3. Virtual Machines (VMs): Independent, isolated environments that run guest


operating systems and applications.

4. Virtualized Resources: CPU, memory, storage, and network are virtually


allocated to each VM.

Virtualization Software Operation:

The operation begins by installing the hypervisor onto the physical hardware. Once the
hypervisor is running, it allows the creation of virtual machines that are assigned virtual
resources. The guest operating systems and applications run on these virtual machines,
which are completely isolated from each other and from the physical hardware.

Step-by-Step Operation:

1. Physical Hardware: The physical server with its resources, such as CPU, RAM,
storage, and network devices.

2. Hypervisor Layer: The hypervisor sits between the hardware and the virtual
machines, managing the allocation of resources.

o For Type 1 Hypervisor: It runs directly on the hardware.

o For Type 2 Hypervisor: It runs on an existing host OS that manages the


hardware.

3. Virtual Machines: The hypervisor creates multiple virtual machines (VMs), each
running its own OS and applications.
12 : Relate the application of server and desktop virtualization in cloud-based
healthcare system.

1. Efficient Resource Utilization and Scalability

Server Virtualization allows multiple virtual servers to run on a single physical machine,
optimizing hardware usage in cloud-based healthcare systems. This means that
healthcare organizations can scale their IT infrastructure according to demand.

2. Data Security and Isolation

Server Virtualization in healthcare systems helps in isolating sensitive patient data from
different applications and users. Each virtual machine (VM) running on the server can
host distinct healthcare applications (e.g., Electronic Health Records, medical imaging,
patient management systems), ensuring that any breach in one VM does not
compromise others.

3. Disaster Recovery and Business Continuity

Server Virtualization in cloud computing enables rapid backup and disaster recovery
solutions for healthcare systems. In case of server failure or disaster, healthcare data
and applications hosted on virtual machines can be restored quickly from backups. This
minimizes downtime and ensures continuity in patient care.

4. Centralized Management and Cost Efficiency

Server Virtualization allows healthcare organizations to centralize their IT infrastructure


management. Healthcare IT administrators can manage and monitor servers,
resources, and workloads from a single console in the cloud. This simplifies the
management of virtual servers, patches, updates, and security configurations.

5. Desktop Virtualization for Healthcare Workers

Desktop Virtualization allows healthcare workers (doctors, nurses, administrative staff)


to access virtual desktops from any device, anywhere, at any time. These virtual
desktops can host medical applications, patient records, and imaging systems,
enabling remote access to clinical information.

6. Simplified Software Updates and Maintenance

Desktop Virtualization in healthcare enables centralized management of operating


systems and software. Healthcare organizations can quickly deploy security patches,
software updates, and new applications across all virtual desktops in the cloud without
needing to update each physical device individually.

You might also like