CLOUD COMPUTING NOTES MID-TERM

ADITYA BATTIN 2020BCS095

Q.1 : Explain convergence of various advances leading to the advent of

cloud computing.
Ans : The development of cloud computing is the result of the convergence of key technological advances in
several areas:

Hardware Advancements:

1. Virtualization: This technology allows multiple virtual machines (VMs) to efficiently share physical
hardware resources, enabling the running of multiple operating systems and software stacks on a single
server, thereby optimizing resource utilization.
2. Multi-core chips: The widespread use of multi-core processors boosted server processing power, making it
feasible to run multiple VMs on a single server, further enhancing resource utilization.

Internet Technologies:

1. Web Services: Open standards for Web services facilitated the integration of diverse applications across
different platforms, offering a standardized method for applications to communicate and share data.
2. Service-Oriented Architectures (SOA): SOA promoted loosely coupled, protocol-independent, and
standards-based distributed computing. It described services in a standardized language, encouraging
interoperability.
3. Web 2.0: The Web 2.0 paradigm emphasized programmable aggregation of information and services,
allowing for the creation of complex applications through the combination of building blocks and APIs.

Distributed Computing and Utility Computing:

1. Grid Computing: Grid computing aimed to aggregate distributed resources for transparent access. It
sought to share compute and storage resources across administrative domains, primarily in scientific
applications, albeit facing challenges in ensuring Quality of Service (QoS) and compatibility.
2. Utility Computing: Utility computing was defined as the on-demand delivery of infrastructure,
applications, and business processes over the Internet. This approach allowed consumers to reduce IT costs
by obtaining services from external providers based on their needs, while providers optimized efficiency and
return on investment.

System Management and Autonomic Computing:

1. Hardware Virtualization: Hardware virtualization, facilitated by hypervisors like VMware, Xen, and KVM,
allowed multiple VMs to run on a single physical server, enhancing isolation, consolidation, and migration
capabilities.
2. Virtual Appliances: Virtual appliances bundled applications with their necessary environments, simplifying
software customization, configuration, and portability. Marketplaces for virtual appliances streamlined
software deployment.
3. Autonomic Computing: The concept of autonomic computing inspired data center automation, where
systems aim to manage themselves with minimal human intervention. Autonomic managers use monitoring
data to make real-time optimizations.

Q.2 : Write a short note on grid and utility computing.

Ans :

Grid Computing:

Definition: Grid computing is a distributed computing approach that aggregates resources from different
administrative domains, allowing transparent access to these resources. Its primary aim is to enhance the
performance of scientific applications, like climate modeling, drug design, and protein analysis, by sharing
computational and storage resources.

Key Aspects:

Standard Web Services: Grid computing relies on standard Web services-based protocols to discover, access,
allocate, monitor, account for, and manage distributed resources as a single virtual system. This
standardization is crucial for efficient grid operation.

OGSA: The Open Grid Services Architecture (OGSA) defines core capabilities and behaviors to address key
concerns in grid systems, promoting uniformity and interoperability.

Examples: TeraGrid and EGEE are prominent production grids that seek to accelerate a range of scientific
applications. These grids enable researchers to harness vast computational resources distributed across
different institutions

Utility Computing:

Definition: Utility computing involves users assigning a "utility" value to their computing jobs, which reflects
their specific requirements, such as deadlines and importance. They pay a service provider based on this
utility, while providers aim to maximize their own utility, often linked to profit. Utility computing creates a
marketplace where resources are allocated based on the perceived value of jobs.

Key Aspects:

Resource Allocation: Utility computing optimizes resource allocation by considering job-specific utility values,
ensuring that higher-value jobs receive prioritized access to resources.

Flexible Resource Management: Users can set their utility value based on their job's specific requirements,
offering flexibility in resource allocation.
Examples: Amazon Web Services (AWS) is a prime example of utility computing, where users pay for
computing resources based on their specific needs. AWS offers a variety of services that can be scaled up or
down as required, making it a cost-effective solution for many businesses.

Q.3 Explain Hardware Virtualization with suitable diagram.

Ans :
Hardware virtualization is a technology that allows multiple operating systems and software stacks
to run on a single physical platform. This is achieved by using a software layer known as the Virtual
Machine Monitor (VMM), or hypervisor, which mediates access to the physical hardware. The
hypervisor presents each guest operating system with a Virtual Machine (VM), which is a set of
virtual platform interfaces.
There are three basic capabilities regarding the management of workload in a virtualized system:

 Isolation: Each program runs in its own isolated space (VM), enhancing security,
reliability, and performance control. Failures in one VM don't affect others.
 Consolidation: Multiple different tasks run on one machine, optimizing system use and
overcoming software and hardware compatibility issues during upgrades.
 Migration: Applications can be moved between machines (migration) for maintenance,
balancing loads, or disaster recovery by packaging the entire state of an operating
system into a VM.

A hardware virtualized server hosting three virtual machines, each one running distinct operating
system and user level software stack.

Several VMM platforms exist that form the basis of many utility or cloud computing environments.
The most notable ones are VMWare, Xen, and KVM.

1. VMWare ESXi: A bare-metal hypervisor from VMWare that installs directly on the physical
server and provides advanced virtualization techniques of processor, memory, and I/O.
2. Xen: An open-source hypervisor that pioneered the para-virtualization concept, allowing the
guest operating system to interact with the hypervisor for improved performance.
 3. KVM (Kernel-based Virtual Machine): A Linux virtualization subsystem that is part of the
mainline Linux kernel, leveraging hardware-assisted virtualization to support unmodified
guest operating systems.

Q.4 Define Atomic computing with its properties.

Ans :
Autonomic computing is a field of research that aims to reduce human involvement in the
operation of complex computing systems. The goal is for these systems to manage
themselves, guided by high-level human input.
Autonomic, or self-managing, systems operate based on several key components:
 Monitoring probes and gauges (sensors): These collect data about the system’s
operation.
 Adaptation engine (autonomic manager): This computes optimizations based
on the data collected by the sensors.
 Effectors: These implement changes in the system based on the optimizations
computed by the autonomic manager.
IBM’s Autonomic Computing Initiative has defined four key properties of autonomic
systems:
1. Self-Configuration: The system can configure itself based on high-level policies
provided by humans.
2. Self-Optimization: The system can optimize its own performance and resources to
achieve the best possible results.
3. Self-Healing: The system can detect and correct faults and problems without
human intervention.
4. Self-Protection: The system can anticipate and protect itself from threats and
attacks.
IBM also suggested a reference model for autonomic control loops of autonomic managers,
called MAPE-K (Monitor, Analyse, Plan, Execute—Knowledge).

Q.5 Explain the cloud computing stack using suitable diagram.

Ans : The cloud computing stack, often referred to as the cloud computing service
models, is a conceptual framework that categorizes cloud computing services into three
distinct layers based on the level of abstraction and the service model provided by cloud
providers.
These layers are explained as follows :
Infrastructure as a Service (IaaS):
 IaaS offers virtualized computing resources like VMs, storage, and networking on
demand.
 Users have control over VM configurations, and it follows a pay-as-you-go model.
 Example: AWS Elastic Compute Cloud (EC2).
Platform as a Service (PaaS):
  PaaS abstracts the underlying infrastructure, providing a development and
deployment platform.
 Developers focus on code, and it offers programming languages and frameworks.
 Example: Google AppEngine.

Software as a Service (SaaS):

 SaaS delivers fully functional software applications over the internet.
 Users access applications via web browsers without installation.
 Example: [Link] for CRM.

Q.6 Enlist and explain the cloud deployment model with suitable diagram.
Ans :
Public Cloud:
Definition: Public clouds are cloud services made available to the general public on a pay-
as-you-go basis.
Explanation: Public clouds are hosted and operated by third-party providers and are
accessible over the internet. They offer a wide range of services to users, who can scale
resources as needed. Users typically have no control over the underlying infrastructure,
making it a cost-effective choice for many organizations.
Private Cloud:
Definition: Private clouds are cloud environments that are set up within an organization's
internal data center and are not accessible to the general public.
Explanation: Private clouds provide the benefits of cloud computing, such as self-service,
scalability, and metered billing, but within the organization's own infrastructure. This
deployment model offers greater control and security, making it suitable for organizations
with specific compliance and security requirements.
Community Cloud:
Definition: Community clouds are cloud environments shared by multiple organizations
with common concerns, such as mission, security requirements, and compliance
considerations.
Explanation: Community clouds are designed to meet the needs of specific communities or
industries. Multiple organizations collaborate to share cloud resources while addressing
shared concerns. This model allows for resource sharing among trusted partners, ensuring
compliance with industry-specific regulations.
Hybrid Cloud:
Definition: Hybrid clouds combine elements of both private and public clouds, allowing
data and applications to move between them as needed.
Explanation: In a hybrid cloud, an organization can leverage its private cloud for sensitive
or critical workloads while using public cloud resources for scalability and flexibility. The
ability to move workloads between these environments is known as "cloud bursting,"
providing a dynamic and cost-effective solution for handling fluctuations in resource
demands.

Types of Cloud based on deployment models

Q.7 Define Cloud and explain its desired features.
Ans :
Definition of cloud computing :
“It is a techno-business disruptive model of using distributed large-scale data centre’s either
private or public or hybrid offering customers a scalable virtualized infrastructure or an
abstracted set of services qualified by service-level agreements (SLAs) and charged only by
the abstracted IT resources consumed.”
1. Self-Service: Cloud users should have on-demand, instant access to resources
without needing human intervention.
2. Per-Usage Metering and Billing: Users should pay only for the resources they
use, on a short-term basis (e.g., hourly), with transparent and efficient pricing,
accounting, and billing.
3. Elasticity: Clouds should provide the illusion of infinite computing resources that
can be rapidly provisioned as needed and released when no longer required, allowing
for scalability.
4. Customization: Cloud resources should be highly customizable to accommodate
the diverse needs of users, whether it involves configuring virtual appliances,
granting privileged access, or providing some level of customization for different
service classes (IaaS, PaaS, SaaS).

Q. 8 Explain Cloud Infrastructure Management. Enlist it's features.

Ans :

Definition: Cloud infrastructure management refers to the process of overseeing and controlling the physical
and virtual resources, such as servers, storage, and networks, within a cloud computing environment.

Cloud infrastructure management involves overseeing physical and virtual resources in a cloud environment,
such as servers and storage.

A virtual infrastructure manager (VIM) is used to orchestrate and optimize these resources, ensuring efficient
provisioning for applications and users.

1. Virtualization Support: Utilizes hardware virtualization for flexible resource partitioning in multi-
tenant data centers.

2. Self-Service Resource Provisioning: Enables users to directly access and customize cloud services
without administrator intervention.

3. Multiple Backend Hypervisors:

• Supports various virtualization technologies, ensuring a uniform management layer.

• Particularly prevalent in open-source VIMs with pluggable drivers.

4. Storage Virtualization:

• Abstracts logical storage from physical devices, creating virtual disks independent of
hardware and location.
• Commonly used with storage area networks (SANs) and storage controllers.
5. Interface to Public Clouds:

• Integrates resources from public clouds to meet varying workload demands.

• Transparence usage of leased resources for applications.

6. Virtual Networking:

• Creates isolated virtual networks like VLANs, enhancing network management and
security.
• Supports secure VPN connections for local and remote VMs.

7. Dynamic Resource Allocation:

• Monitors resource utilization and reallocates resources among VMs to match supply and
demand.
• Aids in energy conservation and SLA optimization.

8. Virtual Clusters:

• Holistically manages groups of VMs for on-demand computing clusters.

• Useful for multi-tier Internet applications.

9. Reservation and Negotiation Mechanism:

• Supports advance reservations and complex leasing terms to meet resource demands.
• Accommodates scenarios where resources are in high demand with negotiation features.

10. High Availability and Data Recovery:

• Offers high availability features to minimize downtime through VM failover.

• Implements redundancy and synchronized VMs for mission-critical applications.
• Utilizes data backup mechanisms, often with incremental backups and proxies, to protect
VM images.

Q.9 Enlist and explain features of IaaS providers.

Ans :

Features of IaaS Providers:

Geographic Presence:
Description: Availability of data centers in multiple locations worldwide to improve availability and
responsiveness.
Examples: Amazon EC2 offers "availability zones" and "regions" distributed across different geographic areas.

Client User Interfaces and Access to Servers:

Description: Various methods for users to interact with cloud services, including graphical user interfaces
(GUI), command-line tools (CLI), and web service (WS) APIs.
Examples: End users often prefer GUIs, while CLI offers flexibility for automation.

Advance Reservation of Capacity:

Description: Ability for users to reserve cloud resources for a specific timeframe in advance.
Examples: Amazon Reserved Instances, which allow users to pay upfront for guaranteed availability over a
specified period.
Service-Level Agreement (SLA):
Description: A commitment by providers to deliver specific Quality of Service (QoS) levels, often including
availability and performance guarantees.
Examples: Amazon EC2 provides an SLA that guarantees a certain percentage of annual uptime.

Hypervisor and Operating System Choice:

Description: Selection of virtualization platforms and supported operating systems.
Examples: Many IaaS providers use hypervisors like Xen, offering a choice between Linux and Windows.

Automated Horizontal Scaling and Load Balancing:

Description: Automatic scaling based on application-specific metrics and distribution of incoming traffic
among available servers.
Examples: Cloud providers like Amazon EC2 offer services like Auto Scaling and Elastic Load Balancing.

Q.10 Enlist and explain features of PaaS providers.

Ans :

Features of PaaS Providers:

Programming Models, Languages, and Frameworks:

Description: PaaS providers offer various programming models and support for multiple programming
languages and frameworks, allowing developers to create applications efficiently.
Examples: Google App Engine supports Python and Java, while Microsoft Azure provides a .NET stack. Heroku
specializes in Ruby on Rails.

Developer Tools:
Description: Tools and development environments that simplify the process of building, deploying, and
managing applications on the platform.
Examples: Google App Engine provides an Eclipse-based IDE, while Microsoft Azure offers tools for Visual
Studio.

Persistence Options:
Description: Methods for storing and retrieving application data, including support for relational databases
and distributed storage solutions.
Examples: Google App Engine uses BigTable, while Salesforce's [Link] uses its own object database.

Automatic Scaling:
Description: PaaS platforms often feature auto-scaling capabilities, enabling applications to adapt
dynamically to varying levels of traffic and resource demand.
Examples: Platforms like Google App Engine and Heroku provide automatic scaling.

Backend Infrastructure:
Description: Information about the underlying infrastructure and services supporting the PaaS, including
components like load balancers, databases, and data storage.
Examples: Google App Engine leverages its own infrastructure, while Microsoft Azure relies on Microsoft's
data centers.
Q.11 Explain challenges and risks of cloud computing.
Ans :

Challenges and Risks in Cloud Computing:

Security, Privacy, and Trust:

 Issue: Cloud services are often public, making them susceptible to attacks.
 Challenges: Ensuring cloud environments are as secure as in-house systems. Trust in providers is
crucial for privacy.
 Legal Considerations: Data centers' physical locations can affect data management and compliance
with local laws.

Data Lock-In and Standardization:

 Concern: Users worry about being locked into one cloud provider, making it hard to move their data.
 Solution: Standardization efforts aim to create open standards for cloud computing. Examples
include the Cloud Computing Interoperability Forum (CCIF) and the Unified Cloud Interface (UCI).

Availability, Fault-Tolerance, and Disaster Recovery:

 User Expectations: Users expect service availability, performance, and clear measures for handling
system failures.
 SLAs: Service Level Agreements (SLAs) are needed to specify service details, including availability and
performance guarantees.

Resource Management and Energy Efficiency:

 Resource Allocation: Efficiently managing physical resources shared among virtual machines is a
challenge.
 Dynamic VM Mapping: Policies for mapping VMs must consider factors like CPU, memory, and
network bandwidth.
 Data Management: Handling large data quantities in VM management activities requires efficient
mechanisms.
 Energy Efficiency: Data centers consume substantial electricity, impacting costs and the environment.
Dynamic resource management can optimize performance and minimize energy consumption.

These challenges and risks must be carefully addressed by cloud providers, developers, and users to ensure
the benefits of cloud computing while mitigating potential issues related to security, data management, and
resource optimization.

Q.12 Explain the promise of the cloud computing services with suitable
diagram.
Ans :

1. Simplicity and Ease of Use: Cloud computing offers simplicity, uniformity, and
ease of use through abstractions, making it accessible without the need to
understand underlying complexities.
2. Economic Savings: Small and medium enterprises can achieve substantial
economic savings by using cloud computing for cyclical IT needs, as documented in
numerous success stories.
 3. Cloudonomics: The economic benefits and trade-offs of leveraging cloud services,
known as "cloudonomics," have become a topic of deep interest among IT managers
and technology architects.
4. Spawning Non-Mission Critical Needs: The promise of the cloud, both in terms
of economics and technology, allows enterprises to move non-mission-critical IT
needs to cloud services, particularly those that are web-oriented, seasonal,
parallelizable, and not highly security-dependent.
5. Successful Adoption by Startups: Many startups have successfully established
their IT departments exclusively using cloud services, achieving high returns on
investment (ROI).
6. Pilots in Large Enterprises: Large enterprises are running successful pilots for
cloud adoption, including experimenting with running complex applications like SAP
on cloud offerings.
7. Predicted Widespread Adoption: Industry analysts predict that a significant
percentage of top enterprises would have migrated the majority of their IT needs to
cloud offerings, demonstrating the widespread impact and benefits of cloud
computing.

The Promise of Cloud Computing Services

Q.13 Draw a suitable diagram for VPC and explain with it's features.
Ans :

Definition : “A Virtual Private Cloud (VPC) is a self-contained, logically isolated virtual

network environment that emulates the structure and functionality of a conventional on-
premises network, providing a scalable infrastructure for deploying and managing
resources.”
 AMAZON Virtual Private Cloud

The following features help you configure a VPC to provide the connectivity that your
applications need:

1. Subnets: Subnets are like address ranges within your virtual private cloud (VPC).
Each subnet is confined to a single Availability Zone and serves as a place to deploy
AWS resources.
2. IP Addressing: You can assign IP addresses (IPv4 and IPv6) to your VPCs and
subnets. You can even bring your existing public IP addresses to AWS and assign
them to your resources, like EC2 instances or load balancers.
3. Routing: Route tables determine where network traffic from your subnets or
gateways should go. They act like roadmaps for directing data within your network.
4. Gateways and Endpoints: Gateways, like internet gateways, connect your VPC to
external networks (e.g., the internet). VPC endpoints enable private connections to
AWS services without exposing them to the internet.
5. Peering Connections: VPC peering lets you connect resources in different VPCs
securely, allowing them to communicate as if they were in the same network.

6. Traffic Mirroring: You can copy network traffic from your instances and send it to
security and monitoring tools for in-depth analysis.
7. Transit Gateways: Think of transit gateways as central hubs that facilitate traffic
routing between your VPCs, VPN connections, and Direct Connect connections. They
simplify network architecture.
 8. VPC Flow Logs: These logs capture details about the IP traffic flowing to and from
network interfaces within your VPC, helping with troubleshooting and security
analysis.
9. VPN Connections: AWS VPN lets you establish secure connections between your
VPCs and your on-premises networks.

Q.14 Draw and explain cloud computing service offering and deployment
models.
Ans :

Cloud Computing Service Offering:

Cloud computing service offerings refer to the types of services and functionalities provided by cloud service
providers to users and organizations. These offerings cater to various user needs, from infrastructure
provisioning to software applications. There are three primary categories of cloud service offerings:

1. Infrastructure as a Service (IaaS):

 Definition: IaaS is a cloud computing service offering that provides virtualized and scalable
hardware resources such as computing power, storage, and network infrastructure.
 Users: Targeted at IT professionals and system administrators.
 Examples: Amazon Web Services (AWS) with services like EC2 (Elastic Compute Cloud) and
S3 (Simple Storage Service).
2. Platform as a Service (PaaS):

 Definition: PaaS is a cloud computing service offering focused on supporting programming

platforms, offering runtime environments that implicitly use cloud services provided by the
vendor.
 Users: Preferred by programmers and developers.
 Examples: Google AppEngine for Java and Python programming, and Microsoft Azure for
.Net development.
3. Software as a Service (SaaS):

 Definition: SaaS on the cloud is about delivering software applications to end-users via the
internet, with underlying cloud infrastructure providing support.
 Users: Architects and end-users of large software packages.
 Examples: [Link], Gmail, Yahoo Mail, Facebook, Twitter, and other cloud-supported
applications.

Cloud Computing Deployment Models:

Cloud computing deployment models refer to how cloud services and resources are implemented, organized,
and managed for use by organizations. There are three primary deployment models:

1. Public Clouds:

 Definition: Public clouds are cloud environments provided by cloud vendors to the general
public or multiple organizations. These environments offer shared resources, such as virtual
servers and storage, over the internet.
 Characteristics: Scalable, cost-effective, and maintained by the service provider.
 Examples: Amazon Web Services (AWS), Google Cloud, Microsoft Azure.
 2. Private Clouds:

 Definition: Private clouds are cloud infrastructures exclusively operated and used by a single
organization. They are hosted on-premises or by a third-party provider, and access is
restricted to that organization.
 Characteristics: Enhanced control, customization, and privacy.
 Examples: On-premises data centers or cloud solutions dedicated to a single enterprise.

3. Hybrid Clouds:

 Definition: Hybrid clouds combine elements of both public and private clouds, allowing data
and applications to be shared between them. Organizations can use hybrid models to meet
specific business needs.
 Characteristics: Flexibility, security, and the ability to balance on-premises and cloud
resources.
 Examples: Combining public cloud services with private data centers or proprietary cloud
solution

Q.15 Explain Challenges in the Cloud with suitable diagram.

Ans :

Challenges in the Cloud:

1 .Simplistic View vs. Complexity: Cloud service offerings present a simplified view of IT, programming,
and resource usage, but the underlying systems face significant complexity and challenges.

2 Underlying System Challenges:

 Failure-Prone: Cloud systems operate in an environment where failures can occur, which
necessitates robust mechanisms for fault tolerance and recovery.
 Heterogeneity: Cloud environments often consist of diverse hardware and software
components, making system management more complex.
  Resource Hogging: Efficient resource allocation and management are essential to ensure
optimal performance.
 Security Shortcomings: Cloud systems must address serious security concerns, such as data
privacy and protection.

3 Idealized View vs. Realistic Management: Cloud services often promise features like network
reliability, instant network latency, and infinite bandwidth, which must be managed realistically to
avoid design and implementation fallacies.

4 Security Challenges: Security is a paramount concern in cloud computing, involving issues related to
data protection, compliance, and trust. The Cloud Security Alliance is actively addressing these
challenge

Q.16 Draw and Explain 7 step model for migration to cloud.

Ans :
The Seven-Step Model for Migration to the Cloud involves a structured and process-
oriented approach to migrating into a cloud environment:
 Conduct Cloud Migration Assessments: Assess and understand all aspects of
the migration, including application, code, design, architecture, and usage levels, as
well as tools, test cases, configurations, functionalities, and non-functional
requirements (NFRs). This leads to a comprehensive migration strategy.
 Isolate the Dependencies: Identify and isolate systemic and environmental
dependencies of enterprise application components within the on-premises data
center to gauge the complexity of the migration.
 Map the Messaging & Environment: Create mapping constructs to determine
what remains in the local data center and what moves to the cloud, considering
messaging and environmental factors.
 Re-architect & Implement the Lost Functionalities: If necessary, re-architect,
redesign, and reimplement parts of the enterprise application on the cloud. Address
any functionality that may be lost during migration.
 Leverage Cloud Functionalities & Features: Utilize the intrinsic features of
cloud computing services to enhance the enterprise application.
  Test the Migration: Thoroughly validate and test the migrated enterprise
application, including components running on the cloud. Address any issues or
challenges that arise during testing.
 Iterate and Optimize: If needed, iterate through the process to optimize the
migration, ensuring it is robust and comprehensive. Continuously refine the
migration approach based on results and feedback.

The Seven-Step Model of Migration into the Cloud.

Q.17 Draw and Explain iterative 7 Step model of migration to Cloud

Ans :
The iterative seven-step model for cloud migration involves a structured approach with a
focus on refining and optimizing the migration process:
 Assessment and Understanding: Initially, assess all aspects of the migration,
including applications, code, architecture, and tools, to formulate a comprehensive
migration strategy.
 Dependency Isolation: Identify and isolate dependencies within the on-premises
data center to gauge migration complexity.
 Mapping Constructs: Create mapping constructs to determine what stays on-
premises and what moves to the cloud, considering messaging and environmental
factors.
 Re-architect and Implement: If needed, re-architect and redesign parts of the
application for the cloud, addressing any potential functionality loss.
 Leverage Cloud Features: Utilize cloud features to enhance the application's
capabilities.
 Testing and Validation: Rigorously test the migrated application, including cloud
components, addressing any issues.
 Iterative Optimization: Continuously iterate and refine the migration approach
based on testing results and feedback, ensuring robustness and comprehensiveness.
 The iterative Seven-step Model of Migration into the Cloud.

Q.18 Derive the equations of cloud migration and deciding cloud

migrations.
Ans :
Deriving the equation for cloud migrating :
At the core of application migration to the cloud, there are typically two scenarios:
1. The application is clean and independent, so it can run unchanged on the cloud.
 2. Some parts of the application need code adjustments or cannot be fully migrated to
the cloud, resulting in a hybrid cloud setup.
Let's define some terms for deriving the equation:
 P: Application before migration running in the captive data center.
 P'c: Part of the application after migration to a hybrid cloud.
 P'l: Part of the application still running in the captive local data center.
 P'ofc: Part of the application optimized for the cloud.
For the second scenario, where only a part of the application is migrated to the cloud, the
equation is as follows:
 (P --> P'c + P'l)
After optimizing the part of the application on the cloud to meet its specific requirements,
the equation changes to:
 (P'c + P'l --> P'ofc + P'l)

Deriving the equation for deciding to cloud migration :

To arrive at a decision to migrate to cloud or not it is a very difficult task. the ROI on
the migration should be posituve for a broad range of pricing varablity.
Lets say that there is an company that wants to move its buesness to cloud. Assuming that
there
are M classes of applications and Each class of questions assigned a certain weightage Bi.
There wass a class with min N questions.
Model the weitage based decision as M x N weightage matrix.

Terms used :
Cl: Lower weightage threshold.
Ch: Higher weightage threshold.
Aij: Specific constant assigned for a question.
Xij: Fraction between 0 and 1 representing the relevance and applicability of the answer to
a question.
Q [Link] a short note on IT as a Service and Integration as a Service.
Ans :

IT as a Service (ITaaS):

 Definition: IT as a Service (ITaaS) is a modern IT delivery model that views IT resources, activities,
and infrastructure as services.
 Service-Oriented Approach: ITaaS transforms every IT element into a service, emphasizing service
orientation principles.
 Design Philosophy: Systems are designed as collections of evolving services, and infrastructures
become service-enabled and collaborative.
 Influence of the Internet: ITaaS is influenced by the pervasive internet, enabling on-demand access
to IT resources.
 Role of Cloud Computing: Cloud computing, especially cloud services, plays a significant role in
realizing ITaaS.
 Consumption-Based Billing: Maturing consumption-based metering and billing capabilities
contribute to the "everything as a service" paradigm.
 Efficient IT Delivery: ITaaS represents a shift in how IT is delivered, providing service-oriented, on-
demand access to IT resources.

Integration as a Service (IaaS):

 Definition: Integration as a Service (IaaS) is a capability offered by cloud platforms to address

business integration requirements.
 Seamless Connectivity: IaaS bridges the gap between cloud-based solutions and on-premises
applications and data sources, ensuring seamless connectivity.
 Security Considerations: Many traditional applications and data sources are locally maintained due
to security concerns.
 Role of B2B Integration: IaaS leverages business-to-business (B2B) integration technology to create a
reliable and secure bridge.
 B2B System Capabilities: B2B systems are traditionally used to automate business processes
between manufacturers and trading partners.
 Features: They provide application-to-application connectivity, encryption for secure data transfer,
data conversion, and data delivery across multiple enterprises.
 Web Infrastructure: IaaS uses this established communication and collaboration model to facilitate
interoperability between cloud and traditional systems over web infrastructure.
Q [Link] SaaS Integration is hard?. Enlist it's constraining attributes and
reasons.
Ans :

Cloud Integration Challenges:

1. New Integration Scenarios:The shift to a cloud model introduces new integration scenarios,
including connecting local applications to the cloud and integrating cloud applications with each
other.
2. Limited Access to Cloud Resources:Access to cloud resources (SaaS, PaaS, and infrastructure) is more
limited than local applications, requiring custom applications designed to support integration.
3. Dynamic Resources Impacting Integration:Dynamic changes in cloud infrastructure and application
versioning can impact integration models, requiring a shift towards Representational State Transfer
(REST) interfaces.
4. Performance Challenges:Network latency becomes an issue in cloud integration due to the dynamic
nature of cloud resources, leading to potential slowdowns in performance.

Constraining Attributes of SaaS Applications:

1. Dynamic Nature of SaaS Interfaces: SaaS applications often have interfaces that constantly change,
making it difficult to maintain integration connections.
2. Dynamic Nature of Metadata Native to SaaS Providers: SaaS providers like [Link] have
dynamic metadata that can change, requiring frequent adjustments to integration mechanisms.
3. Managing Assets Outside the Firewall: SaaS applications may exist outside the organization's
firewall, making integration and data synchronization more complex.
4. Massive Data Transfer and Data Quality:The need to transfer massive amounts of data between
SaaS and on-premise systems daily can lead to data quality and integrity issues.

Q [Link] suitable diagram explain Cloud Integration Scenarios.

Ans :

1. Public Cloud Integration (Figure 3.1):

 Scenario: Within a public cloud, two different applications are hosted.

 Integration Middleware Role: Cloud integration middleware (e.g., cloud-based ESB or ISB) facilitates
seamless communication between these applications.
 Ownership: The applications may be owned by two different companies.
 Virtualization: They may run on the same physical server but operate in different virtual machines.
2. Homogeneous Cloud Integration (Figure 3.2):

 Scenario: Applications to be integrated are in two geographically separated cloud infrastructures.

 Integration Middleware Location: The integration middleware can be in cloud 1, cloud 2, or a
separate cloud.
 Transformation: Data and protocol transformation is required, and it's typically performed by the
ISB.
 Compatibility: This approach aligns with enterprise application integration procedures.

3. Heterogeneous Cloud Integration (Figure 3.3):

 Scenario: One application resides in a public cloud, while the other is in a private cloud.
 Current Dominating Scene: This scenario is currently prevalent in cloud integration, where
businesses subscribe to popular on-demand enterprise packages from established providers.
 Examples: Businesses adopt on-demand solutions like [Link]'s CRM or NetSuite's ERP.

Future Trends:
 As the cloud landscape evolves, the first two scenarios are expected to become more prevalent when
multiple commercial clouds and cloud services become pervasive.
 This will make service integration and composition a crucial factor in global computing.
Q [Link] and explain the integration methodologies.
Ans :

1. Traditional Enterprise Integration Tools with Special Connectors:

 Approach: Traditional enterprise integration tools are enhanced with specialized connectors to
access cloud-located applications.
 Suitability: Ideal for IT organizations with existing investments in integration suites. Special drivers,
connectors, and adapters are added to the existing integration platforms to enable bidirectional
connectivity with cloud services.
 Integration Appliances: Integration appliances are popular for enhanced performance.
2. Traditional Enterprise Integration Tools Hosted in the Cloud:

 Approach: Similar to the first option, but the integration software suite is hosted in third-party cloud
infrastructures.
 Benefits: Suitable for IT organizations outsourcing integration projects to service providers who have
the expertise to create and deliver integrated systems. Eliminates concerns about hardware
procurement, software installation, and maintenance.
 Use Cases: Well-suited for cloud-to-cloud (C2C) integration, requiring a secure VPN tunnel to access
on-premise corporate data.
 Example: Informatica PowerCenter Cloud Edition hosted on Amazon EC2.
3. Integration-as-a-Service (IaaS) or On-Demand Integration Offerings:

 Approach: These are SaaS applications designed to securely deliver integration services over the
Internet. They facilitate the integration of cloud applications with on-premise systems and cloud-to-
cloud applications.
 Suitability: Ideal for companies prioritizing ease of use, maintenance, rapid deployment, and cost-
effectiveness. Appeals to small and mid-sized companies, as well as large enterprises with
departmental application deployments.
 Resource Utilization: This approach allows SaaS administrators or business analysts to manage and
maintain integration work.
 Example: Informatica On-Demand Integration Services.

Additional Integration Methods and Middleware Products:

1. Hosted and Extended ESB (Internet service bus / cloud integration bus): Using hosted and extended
enterprise service buses for integration.

2. Online Message Queues, Brokers, and Hubs: Utilizing message-based integration mechanisms.

3. Wizard and Configuration-Based Integration Platforms (Niche Integration Solutions): Leveraging

platforms that offer integration through configuration and wizards.

4. Integration Service Portfolio Approach: Employing a portfolio of integration services.

5. Appliance-Based Integration (Standalone or Hosted): Using appliance-based solutions for

integration, which can be standalone or hosted.
Q [Link] and Explain Characteristics of Integration Solutions and
Products.
Ans :

Characteristics of Integration Solutions and Products:

1. Connectivity:
 Definition: Connectivity refers to the integration engine's ability to interact with both source
and target systems using their native interfaces.
 Variety of Interfaces: Integration engines must leverage the interfaces provided by systems,
which can range from standards-based interfaces like Web services to older and proprietary
ones.
 Responsibility: The connected systems are responsible for externalizing correct information
and internalizing information processed by the integration engine.
2. Semantic Mediation:
 Definition: Semantic mediation involves accounting for the differences in application
semantics between two or more systems. Semantics refers to how information is
understood, interpreted, and represented within information systems.
 Handling Differences: When linking different and distributed systems, semantic mediation
covers the differences in their distinct semantics.
3. Data Mediation:
 Definition: Data mediation involves converting data from a source data format into a
destination data format.
 Coupled with Semantic Mediation: Data mediation, or data transformation, is the process of
converting data from one native format on the source system to another data format for the
target system.
4. Data Migration:
 Definition: Data migration is the process of transferring data between storage types,
formats, or systems.
 Mapping and Transformation: Data migration involves mapping data from the old system to
the new system, often using data extraction and data loading technologies.
5. Data Security:
 Definition: Data security ensures that information extracted from source systems is securely
placed into target systems.
 Leveraging Native Security: Integration methods must use the native security systems of
source and target systems, mediate differences, and securely transport information between
connected systems.
6. Data Integrity:
 Definition: Data integrity ensures that data is complete and consistent.
 Guarantee During Integration: Integrity must be guaranteed during data mapping and
maintenance in integration operations, such as data synchronization between on-premise
and SaaS-based systems.
7. Governance:
 Definition: Governance refers to the processes and technologies that control how systems
are accessed and leveraged.
 Integration Perspective: In the context of integration, governance involves managing
changes to core information resources, including data semantics, structure, and interfaces.
Q [Link] Data Integration Engineering Lifecycle.
Ans :

Data Integration Engineering Lifecycle:

The data integration engineering lifecycle is a structured process for integrating data from various sources
and systems. This lifecycle involves several key phases, each of which plays a crucial role in ensuring
successful data integration:
1. Understanding:
 Definition: This phase involves understanding the problem domain by defining the metadata
native within both the source and target systems.
 Semantic Understanding: It aims to achieve a complete semantic understanding of both the
source (e.g., [Link]) and target systems (e.g., an on-premise inventory system).
 Relevance to Multiple Systems: If there are multiple systems for integration, the same
practice must be applied to each to understand their semantics.
2. Definition:
 Definition of Information: In this phase, the information gathered during the understanding
phase is defined at a high level. This includes what the information represents, ownership,
and physical attributes.
 Enhanced Perceptive: This step contributes to a better understanding of the data beyond
simple metadata, ensuring that the integration process proceeds in the right direction.
3. Design:
 Designing Integration Solution: The design phase focuses on designing the integration
solution for moving data from one point to another while accounting for semantic
differences.
 Data Transformation and Mediation: It involves using the data transformation and
mediation layer to map the schema from the source to the schema of the target.
 Visual-Mapping Technology: Visual-mapping technology is increasingly used in this phase.
Security and governance concepts are also considered in the design of the data integration
solution.
4. Implementation:
 Actual Implementation: Implementation refers to the actual implementation of the data
integration solution using the selected technology.
 Connecting Systems: This phase involves connecting the source and target systems and
implementing the integration flows as designed in the previous step.
 Getting the Solution Running: Other necessary steps are taken to get the data integration
solution up and running.
5. Testing:
 Assuring Proper Design and Implementation: Testing ensures that the integration is properly
designed and implemented and that data synchronizes correctly between the systems
involved.
 Monitoring Information Flow: It involves monitoring how information flows from the source
system to the target system using known test data.
 Data Mediation Mechanism: Ensuring the correct functioning of data mediation
mechanisms and reviewing overall performance, durability, security, modifiability, and
sustainability of the integrated systems.
Q [Link] Jitterbit and draw diagram for it's application linkages.
Ans :

Jitterbit Overview:

Jitterbit is a fully graphical integration solution designed to facilitate the integration of [Link], a Platform
as a Service (PaaS), with other on-demand or on-premise enterprise applications, databases, and legacy
systems. It offers a versatile platform and productivity tools to reduce the complexities of integration efforts.

Jitterbit Components:

1. Jitterbit Integration Environment:

 Graphical User Interface (UI): Provides a user-friendly, point-and-click interface for
configuring, testing, deploying, and managing integration projects.
 Quick Configuration: Allows for the rapid design of integration projects through the graphical
environment.
2. Jitterbit Integration Server:
 Run-Time Engine: A powerful and scalable engine for processing integration operations. It is
fully configurable and manageable through the Jitterbit application.

Integration Benefits:
 Simplified Integration: Jitterbit simplifies the integration of [Link] with various on-premise
systems, including ERP, databases, flat files, and custom applications.
 Versatility: It enables connections between [Link] and a wide variety of systems.
 Reduces Integration Efforts: Jitterbit's productivity tools reduce the time and effort required for
integration projects.

Application Linkages:

 Jitterbit seamlessly connects various enterprise systems with on-demand applications like [Link].
 Acts as a bridge, enabling data synchronization and integration between these systems.
Q [Link] and Explain The Pervasive Data Cloud.
Ans :

The Pervasive DataCloud:

Pervasive DataCloud is a unique multi-tenant platform designed to provide dynamic "compute capacity in the
sky" for deploying on-demand integration and other data-centric applications. It stands out as the first multi-
tenant platform delivering various services, as follows:

1. Integration as a Service (IaaS): Offers integration for both hosted and on-premises applications and
data sources.
2. Packaged Turnkey Integration: Provides highly affordable, subscription-based, packaged integration
solutions, simplifying the integration process.
3. Supports Every Integration Scenario: Adapts to various integration needs, including data migration,
consolidation, conversion, ETL, B2B, EAI, SaaS, cloud, SOA, and more.
4. Connectivity to Hundreds of Applications and Data Sources: Enables connections to a wide range of
applications and data sources for comprehensive data management.

Key Components of Pervasive DataCloud:

 Pervasive DataSynch Family: Offers turnkey cloud-based integration solutions for popular
applications like Salesforce, QuickBooks, and Microsoft Dynamics.
 Pervasive Data Integrator: A design-once and deploy-anywhere solution supporting all integration
scenarios, including data migration, ETL, B2B, EAI, SaaS, and more.

Pervasive DataCloud Characteristics:

 Multi-Tenant: Supports multiple users and applications, accommodating diverse data-centric

solutions, and handles fluctuating data volumes.

 Flexibility: Enables integration between SaaS-to-SaaS, SaaS-to-on-premise, or on-premise-to-on-

premise, catering to various integration requirements.

 Accessibility and Configuration: Allows customers to access, configure, and run integration solutions
via a web browser for ease of use.

 Robust: Offers automatic updates and monitoring, ensuring efficient result tracking by account,
application, or user.

 Security: Utilizes advanced technologies and secure data centers to maintain the service's security
and availability.

 Affordability: Adopts a pay-as-you-go model for delivering packaged solutions, making it cost-
effective.
Q [Link] and Explain .NET Service Bus and .NET Relay Service.
Ans :

Azure, Microsoft's cloud operating system, streamlines web and Windows application development,
deployment, and delivery. Azure features two primary components:

.NET Service Bus:

 Service Bus: Provides hosted, secure, and broadly accessible infrastructure for communication, event
distribution, naming, and service publishing.
 Service Bus Relay: Allows services to be exposed securely through a relay, providing connectivity
options for endpoints that might be behind network address translation (NAT) boundaries or have
dynamically assigned IP addresses.
 Access Control Service: Offers hosted, secure, standards-based infrastructure for authentication and
authorization, supporting both simple user name/password authentication and more complex,
federated authorization scenarios.
 Workflow Service: Hosts service orchestration using Windows Workflow Foundation (WWF) for rules-
based control flow, service invocation, and message processing.

.NET Relay Service:

 Challenges in Service Connectivity: Many services are located behind firewalls and load balancers,
with dynamic and intranet-only addresses, causing issues with scalability, availability, and security.
 Solution with Relay Service: Azure provides a relay service in the cloud, acting as an intermediary to
facilitate connectivity and relay calls to the service.
 Client-Service Connection: Instead of connecting clients directly to the service, the relay service acts
as an intermediary, resolving connectivity challenges.
 Connectivity Requirements: For the relay service solution to work, both the client and service
intranets need to allow connections to the cloud.
Q [Link] Cloud- based Enterprise Mashup Integration Platform
Architecture.
Ans :

The Cloud-based Enterprise Mashup Integration Platform Architecture is a framework that enables the
creation of mashups within an enterprise context.

Key Components:

Mashup Integration Services: These are the core services that enable mashup creation. They include
components like identity management, error handling, translation engine, routing engine, message queue,
and more.

Mashup Platforms: These are the tools or platforms that users choose to create their mashups. Users access
the mashup integration services through their chosen mashup platform.

Identity Management: This service verifies and manages user identities, ensuring that only authorized users
can access the system.

Error Handling and Monitoring: It tracks the flow of messages, detects errors, and collects statistical data for
monitoring and troubleshooting.

Translation Engine: This service is responsible for translating data between different formats and protocols to
ensure compatibility among different mashup platforms.

Routing Engine: The core of the integration services, it processes incoming messages, applies rules
configured by users, and forwards the messages to the right recipients.
Message Queue: A storage service that holds messages until they can be processed. It allows for
asynchronous message handling.

Persistent Storage: Large data, such as files, can be stored here. Amazon S3 is mentioned as an example of a
service that provides this functionality.

How it Works:

1 Users access the services through their chosen mashup platform.

2 Before processing any message, the system checks the sender's access rights to ensure they are
authorized.
3 If the sender is authorized, the message is placed in the message queue.
4 If necessary, the message is translated into the appropriate format.
5 The routing engine determines the recipient based on configured rules.
6 Successful message delivery is logged, and any errors are recorded.
Q [Link] The Framework Architecture of Sensor—Cloud Integration.
Ans:

The Framework Architecture of Sensor—Cloud Integration is designed to link wireless sensor networks
(WSNs) with cloud-based applications. It aims to enable the utilization of sensor data for various community-
centric applications on the cloud. Here's a simplified explanation of its components and how it works:

Key Components:

1. Wireless Sensor Networks (WSNs): These are networks of small, smart devices that collect data from
the physical world, such as temperature, light, and pressure.
2. Gateways: These devices serve as bridges between WSNs and the cloud, transmitting sensor data to
the cloud infrastructure.
3. Sensor Cloud Provider (CLP): The cloud infrastructure that hosts the sensor data and applications.
4. Pub-Sub Broker: A critical component that receives and distributes sensor data to subscribers
(applications and users).
5. Stream Monitoring and Processing Component (SMPC): Monitors sensor data streams and performs
real-time processing based on the nature of the data.
6. Registry Component (RC): Stores user subscriptions for sensor data and manages which data types
are needed by each application.
7. Analyzer Component (AC): Determines which applications require sensor data and how it should be
delivered (periodic or immediate).
8. Disseminator Component (DC): Delivers sensor data to subscribed users and applications, leveraging
the event matching algorithm.

How it Works:

1. User Registrations: Users register their information and subscriptions for sensor data with various
cloud-based applications (SaaS).
2. Sensor Data Input: Sensor data, collected from the physical world through WSNs and gateways,
enters the system.
3. Stream Monitoring and Processing: The system checks if incoming sensor data requires real-time
processing. If yes, SMPC processes the data; otherwise, it is stored for periodic or immediate
delivery.
4. Application Identification: The AC identifies which applications need the sensor data and how
urgently.
5. Event Matching: The DC uses an event matching algorithm to find subscribers for each application
and delivers the data to them.
6. Cloud Infrastructure: All these processes are managed within the cloud infrastructure, which ensures
high performance and scalability.

The framework's components work in harmony to enable the integration of sensor networks with cloud-
based applications. The pub-sub model simplifies data exchange and allows seamless communication
between WSNs and traditional networks, as well as between different WSNs. This architecture opens the
door to innovative community-centric sensing applications, with the cloud as the central hub for data
processing and distribution.
Q [Link] any three services provided by AWS Cloud.
Ans :

Amazon Web Services (AWS) offers a wide range of cloud services. Here are explanations of three key
services provided by AWS:

Amazon EC2 (Elastic Compute Cloud):

 Amazon EC2 is one of the foundational services offered by AWS. It provides scalable and resizable
virtual servers, known as instances, in the cloud. These instances can be easily launched and
managed to meet various computing needs.
 Users can choose the type of instance (e.g., compute-optimized, memory-optimized, storage-
optimized) and the operating system they want to run.
 EC2 instances can be used for a wide range of applications, from hosting websites and running web
applications to performing complex data analysis and machine learning tasks.
Amazon S3 (Simple Storage Service):
 Amazon S3 is a highly scalable and durable object storage service. It allows users to store and
retrieve data, including documents, images, videos, and backups, over the internet.
 S3 offers different storage classes to optimize costs based on the data access patterns. For example,
users can choose Standard for frequently accessed data, or Glacier for archiving.
 S3 is known for its high availability and redundancy, making it a reliable option for businesses to store
their critical data.
Amazon RDS (Relational Database Service):
 Amazon RDS is a managed relational database service that supports various database engines, such
as MySQL, PostgreSQL, Oracle, SQL Server, and MariaDB.
 RDS automates routine database tasks, including provisioning, patching, backup, recovery, and
scaling, allowing developers to focus on building applications rather than managing databases.
 It is an excellent choice for businesses that require a robust, scalable, and highly available database
solution without the operational overhead of managing the underlying infrastructure.