Alternative: In most cases your application is probably somewhere between isolated and completely integrated with other applications. In this case, here are some options based on the nature of the dependency:
- Communication channel dependency - Create a distributable communication channel that is secure
- Architecture dependency - Make a copy of the shared layer for the cloud
- Single sign-on security - Upgrade single sign-on to support remote sign-on
2. Your application architecture is cloud friendlyAny application on an x86 platform would work well in the cloud regardless of the operating system. If the application is on some platform other than x86 and you still want to go cloud, then you would need to re-architect the application to the x86 platform before you begin migration.
Also, if the online-architecture is web based or client server, then your application is more cloud friendly. Moreover, if the online-architecture is heterogeneous from the batch-architecture, then your application is even more cloud friendly.
Alternative: If your application is on any other platform (such as Sun Sparc, Power PC, or Mainframe), then it might be a better candidate for managed hosting. Another reason to opt for managed hosting is if your servers require software licenses that can only be tied to physical cores.
3. Your application security requirements are satisfied by FISMA complianceSome cloud providers are FISMA (Federal Information Security Management Act) certified which ensures they are satisfying all the Federal security standards as measured by NIST. In addition to FISMA compliance, security can be further enhanced by engaging managed services for security on the cloud (like netForensics).
Alternative: If it is necessary for all the data and/or hardware to be located on-site, then a private cloud or a public/private hybrid may be an option.
<- Back to Part 1 - Your application may NOT YET be ready for the Public Commodity Cloud if...