• No products in the cart.


There can be business needs as well as technological reasons behind the migration into

cloud computing. Consumers may choose to migrate their in-houses or outsourcing (non

cloud computing) facilities into cloud. Migration may happen at various levels of computing

and depending on them the migration into cloud can be done in IaaS, PaaS or SaaS offerings.

Among them, generally the migration of traditional application into SaaS is the most common

and important concern for enterprises.

The application migration can happen in various forms. First, the entire application

may be imported to cloud in its original form. Second, some minor changes may have to be










Economies of scale

Consumer’s control

FIG 19.3: A single window view of cloud computing environment


e Flexibility of us331

Cloud Management and a Programming Model Case Study

incorporated in the code of an application in order to make it adaptable before migrating

into cloud. Third, the application may require re-designing and re-implementation. Thus,

it may need re-coding of the application again from the scratch. And finally, the whole

architecture may require changing. Besides these, for any form of application migration, all

of its usages have to be migrated into the cloud which will in turn need suitable adaptations

and modifications. In brief, the migration of an application from non-cloud environment

into cloud can happen in one of the five above mentioned forms: application, code, design,

architecture and usage.

19.4.1 Phases of Migration

Migration into cloud must follow a structured and integrated approach. Technologists have

recommended a few sequential phases for migrating the applications to cloud. The seven phases

have been identified in this process are mentioned below:

1. Assessment: The first step in assessment is the study on return on investment (ROI).

Complexity of migration is another matter for consideration here. The assessment may

involve with some issues at the application, code, design and architecture level.

2. Isolation: Traditional applications must be isolated from their environmental (that is the

computing system environment) dependencies.

3. Mapping: Features are identified to be moved into cloud and those need to be retained as

in earlier environments.

4. Rebuilding: The part which moves into cloud may need to be re-coded, re-designed or

re-created as per the requirements.

5. Augmentation: This feature in cloud computing service (contrary to non-cloud system) is

used to increase the efficiency and capacity of the applications.

6. Testing: Testing of the new form of the application is carried out before moving it into the


7. Optimization: Depending on the result of testing, some optimizations may be needed.

This phase may go in an iterative way as long as the migration is successful.

A well planned migration into cloud provides significant advantages and opens up doors for

new opportunities. It cuts down capital expenses (Capex) for computation and also reduces

operational expenses (Opex).

Template Design © VibeThemes. All rights reserved.