You are on page 1of 5


Given that cloud computing is a “techno-business disruptive model” migrating into
the cloud is poised to become a large-scale effort in leveraging the cloud in several
enterprises. “Cloudonomics” deals with the economic rationale for leveraging the
cloud and is central to the success of cloud-based enterprise usage. 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 dilemmas when planning
for new Enterprise IT initiatives.
Most users of cloud computing services offered by some of the
large-scale data centers are least bothered about the complexities
of the underlying systems or their functioning They were most
impressed by the simplicity, uniformity, and ease of use of the
Cloud Computing Service abstractions. In small and medium
enterprises, cloud computing usage for all additional cyclical IT
needs has yielded substantial and significant economic savings.
This economics and the associated trade-offs, of leveraging the
cloud computing services, now popularly called “cloudonomics,”
for satisfying enterprise’s seasonal IT loads has become a topic of
deep interest amongst IT managers and technology architects.
As shown in Figure the promise of the cloud both on the business
front (the attractive cloudonomics) and the technology front.
Invariably, these IT needs had some common features: They were
typically Web-oriented; they represented seasonal IT demands;
they were amenable to parallel batch processing; they were nonmission critical and therefore did not have high security demands.

Why Migrate? There are economic and business reasons why an enterprise application can be migrated into the cloud. Adoption of or integration with cloud computing services is a use case of migration. or the design (and therefore the code) needs to be first migrated into the cloud computing service environment. or finally perhaps the migration results in the core architecture being . or perhaps some degree of code needs to be modified and adapted. Many of these efforts come up as initiatives in adoption of cloud technologies in the enterprise. so it runs as is. migration of an application into the cloud can happen in one of several ways: Either the application is clean and independent. resulting in integration of enterprise applications running off the captive data centers with the new ones that have been developed on the cloud.Companies want to migrate to cloud because of following reasons  Security Performance Monitoring Consistent  Robust Service abstractions Meta Scheduling  Energy efficient load balancing Scale management  SLA & QoS Architectures Interoperability  Portability Green IT  Full Network Reliability  Zero Network Latency  Infinite Bandwidth  Secure Network  No Topology changes  Centralized Administration  Zero Transport Costs  Homogeneous Networks & Systems At the core. and there are also a number of technological reasons.

then the case for migration into the cloud is strong. the migration of the enterprise application P can happen at the five levels of application. It can be that the P’l migration happens at any of the five levels without any P’l component. Apart from these costs. when the entire application is migrated onto the cloud. Most cloud service vendors. After due study and practice. at a broad level. it is the usage of the application that needs to be migrated and therefore adapted and modified. code. the migration of an enterprise application is best captured by the following: where P is the application before migration running in captive data center.With due simplification. P’l is the part of application being run in the captive local data center. this resulting in a new architecture being developed. code. architecture. or the elastic bandwidth.migrated for a cloud computing service setting. then P’l is null. and therefore the cloudonomics of migration should be soundly meaningful accommodating the pricing variability. P ‘c the application part after migration either into a (hybrid) cloud. THE SEVEN-STEP MODEL OF MIGRATION INTO A CLOUD Typically migration initiatives into the cloud are implemented in phases or in stages. we share the Seven-Step Model of . and usage. migration can happen at one of the five levels of application. the elastic storage. Of course these pricing tariffs can be variable too. Indeed. other factors that play a major role in the cloudonomics of migration are the licensing issues (for perhaps parts of the enterprise application). it could result in some parts being run on the captive local data center while the rest are being migrated into the cloud—essentially a case of a hybrid cloud usage. Or perhaps while the application is migrated as is. and P’OFC is the application part optimized for cloud. design. At the core of the cloudonomics. In brief. and the pricing of the cloud service offerings. If an enterprise application cannot be migrated fully. However. If the average costs of using an enterprise application on a cloud is substantially lower than the costs of using it in one’s captive data center and if the cost of migration does not add to the burden on ROI. architecture. have tariffs for the kind of elastic compute. Compound this with the kind of cloud computing service offering being applied—the IaaS model or PaaS or SaaS model—and we have a variety of migration use cases that need to be thought through thoroughly by the migration architects. A structured and process-oriented approach to migration into a cloud has several advantages of capturing within itself the best practices of many migration projects. design. and usage. along with the accompanying design and code implementation. the SLA compliances.

1. In a succinct way. The first step of the iterative process of the seven-step model of migration is basically at the assessment level. and NFRs of the enterprise application. or usage levels. Perhaps a substantial part of the enterprise application needs to be rearchitected. the architecture. In addition. in turn. Cloud migration assessments comprise assessments to understand the issues involved in the specific case of migration at the application level or the code. the test cases as well as configurations. migration assessments are done for the tools being used. one then goes about generating the mapping constructs between what shall possibly remain in the local captive data center and what goes onto the cloud. After isolation is complete. functionalities. Proof of concepts or prototypes for various approaches to the migration along with the leveraging of pricing parameters enables one to make appropriate assessments. the design. . while Figure 2 captures the iterative process of the seven-step migration into the cloud. These assessments are about the cost of migration as well as about the ROI that can be achieved in the case of production version.Migration into the Cloud as part of our efforts in understanding and leveraging the cloud computing service offerings in the enterprise context. Figure1 captures the essence of the steps in the model of migration into the cloud. This results in a meaningful formulation of a comprehensive migration strategy. yields a picture of the level of complexity of the migration.2 The next process step is in isolating all systemic and environmental dependencies of the enterprise application components within the captive data center. Fig 2. FIGURE 2. This.

Due to this migration. Our best practices indicate that it is best to iterate through this Seven-Step Model process for optimizing and ensuring that the migration into the cloud is both robust and comprehensive. These test results could be positive or mixed. we iterate and optimize as appropriate. Though not comprehensive in enumeration. After several such optimizing iterations. Having done the augmentation. it is possible perhaps that some functionality is lost.3 . This gets in just about the functionality of the original enterprise application. it is representative Fig 2. Figure 2. the migration is deemed successful. In the latter case.3 captures the typical components of the best practices accumulated in the practice of the Seven-Step Model of Migration into the Cloud. In the next process step we leverage the intrinsic features of the cloud computing service to augment our enterprise application in its own small ways.redesigned. and reimplemented on the cloud. we validate and test the new form of the enterprise application with an extensive test suite that comprises testing the components of the enterprise application on the cloud as well.