Transformation to the Cloud involves applying the right strategy to the right application while substituting the right components coupled with the right integration to ensure the right level of service. To have a holistic approach to Transformation, all these rights need to synthesize effectively. Applications Rationalization is a key starting point to ensure that these "Rights" are exercised properly.
Listed below are the – shall we say -- Cloud Transformation Bill of Rights!
1) Right application. When reviewing the suitability of an application for Cloud Computing, there are several aspects that need to be considered including: a) federal regulations on data, b) Compliance laws, c) security requirements , d) nature of the application functionality, e) degree of fluctuation in demand for resources and f) latency. The manner in which these aspects manifest themselves establishes the overall suitability of an application for deployment to the Cloud.
2) Right Transformation. In my recent post, How you know it is time to retire an application, I outline various aspects that project an application as being a good candidate for retirement. Such an application is not suited for modernization in general, let alone transformation to the cloud. Some applications could make do with a modernization of the user interface. Applications that duplicate other functionality already available within the enterprise could be consolidated. Applications targeted for re-engineering have to be reviewed for their applicability to the Cloud environment. In other words, the transformation approach for every application has to be evaluated in its own merit.
3) Right Substitution. The modernized environment for an application need not be within the firewalls of the enterprise. Thanks to the Cloud, third-party service providers are increasingly becoming an option in comparison with yester-years. Applications that have functionality that can be easily substituted with services provided by other vendors are usually better suited for transformation to the Cloud. Thus, resident mechanisms enabling key functionality within the enterprise can be substituted with the appropriate alternative.
4) Right Integration. There are a lot of moving parts to Transformation. Decisions made on one applications impact its integration with other applications. One must not lose sight of the integration needs that continue to exist within the Cloud. Applications and services deployed to the Cloud should continue to enjoy the requisite levels of integration so that they can co-exist upon a cohesive, well-knit fabric across the enterprise.
5) Right Service. Applications deployed to the Cloud must continue to provide the expected level of service to end users to whom the deployment environment is really not a concern. To that end, enterprises must ensure that the appropriate checks and balances are in place so that the end users can continue to enjoy the expected service levels even after the applications have been deployed to the cloud.
Every one of these "Rights" must be exercised for an effective Transformation to the Cloud. Those are the "Rights" that come to my mind.
Are there other "Rights" that come to your mind? You certainly have a right to share your thoughts.
Additional Cloud Transformation Resources: