Cloud Computing

L E C T U R E R : P R O F, WA S I M U L L A H S A F I
E M A I L : WA S I M S A F I 5 0 4 @ G M A I L . C O M
C O N TA C T N U M B E R : 0 7 6 5 2 4 2 6 1 9
Cloud Computing
Why Migrate?
Continued….
At what IT costs—both short term and long term—would one want to
migrate into the cloud?
While all capital expenses are eliminated and only operational expenses
incurred by leveraging the cloud, does this satisfy all strategic
parameters for enterprise IT?
Does the Total Cost of Ownership (TCO) become significantly less as
compared to that incurred when running one’s own private data
center?
Decision-makers, IT managers, and software architects are faced with
several problems when planning for new Enterprise IT initiatives.
Why Migrate?
There are economical and business reasons why an
enterprise application can be migrated into the cloud, and
there are also a number of technological reasons.
Many of these efforts come up as initiatives in adoption of
cloud technologies in the enterprise, resulting in integration
of enterprise applications running off the captive data
centers with the new ones that have been developed on the
cloud.
Adoption of or integration with cloud computing services is
a use case of migration.
 Ways of Migration
At the core, migration of an application into the cloud can happen in one of
several ways:
1) Either the application is clean and independent, so it runs as is;
2) Some degree of code needs to be modified and adapted; The design (and
therefore the code) needs to be first migrated into the cloud computing
service environment.
3) Perhaps the migration results in the core architecture being migrated for a
cloud computing service setting, this resulting in a new architecture being
developed, along with the accompanying design and code
implementation.
4) While the application is migrated as is, it is the usage of the application
that needs to be migrated and therefore adapted and modified.
In brief, migration can happen at one of the five levels of application,
code, design, architecture, and usage
 Cloud migration
Cost of migration: is it economically feasible or tenable?
 License fee: SLA compliance

Price of the cloud offerings

Pay per use: lower cost barrier
On demand resources
Auto-scaling
CAPEX vs OPEX: no capital expenses (CAPEX) and only operational
expenses (OPEX).
SLA driven operations: much lower TCO (Total cost of ownership).
Continued….
Infinite elastic availability
Compute/storage/bandwidth
Automatic usage monitoring.
Jobs/tasks virtualized and transparently movable
Integration and interoperability support for hybrid
operations
Abstracted IT features
Seven-step model of migration
Conduct cloud migration assessment
 Understand the migration issues at the application level or
the code, the design, the architecture, or usage levels
 Cost of migration: ROI (Return of investment)
Isolate the dependencies
 Isolate all systematic and environmental dependencies of
the enterprise application components within the captive
data center.
Seven-step model of migration
Map the messaging and environment
 Message map: displaying detailed, hierarchically organized
responses to anticipated questions or concerns
Generate the mapping constructs between what shall
remain in the local captive data center and what goes onto
the cloud.
Re-architect and implement the lost functionalities
Perhaps some functionality may be lost due to migration
Some part of the enterprise application may need to be re-
architect, redesigned, and re-implemented on the cloud.
 Continued….
Leverage cloud function and
features
Control the inherent features of the
cloud computing service to
augment/enlarge the enterprise
application

Test the migration

 Test the new form of the enterprise
application (both on the captive data
center and on the cloud as well)

Iterate and optimize

 Iterate and optimize the process
Seven step model steps further
examples
 Migration risks and Mitigation/Improvement

Two categories of risk:

1) General migration risks:
 Performance monitoring.
 Business continuity and disaster recovery of the cloud computing
service
 Compliance with standards and governance issues
 Licensing issues
 Ownership, transfer, and storage of data in the application
 Portability and interoperability issues that would mitigate potential
vendor lock-ins.
Continued….
2) Security-related migration risks:
 Trust and privacy
 The right to obtain execution logs and audit trails as a
detailed level
 Problems due to multi-contract
 Data leakage
Thanks