Hybrid Cloud Requirements, Part 2
Curator's Note: The content of this article was originally written back in December of 2012 by Anand Iyengar on the Cloud Velocity blog.
Last month we wrote about hybrid cloud requirements in an effort to encourage more focus on core capabilities.
The first requirement had to do with new and existing multi-tier apps. Our rationale: a true hybrid cloud should handle all apps and not be limited to new apps created just for the cloud. Understandably, enterprises will be unlikely to deploy tier-one apps into the cloud in the short term, but the ability to deploy and operate them in the cloud when desired, should be a critical hybrid cloud requirement.
The second requirement had to do with the vital role of critical network services in the hybrid cloud. Without hybrid cloud integration to enable services to run seamlessly between clouds and data centers, apps are limited to operating in isolated public or private clouds.
The third requirement had to do with lock-in avoidance, which includes having to standardize on a single virtualization vendor platform, or having to modify apps to run on a specific vendor’s cloud.
These requirements are more than just technology requirements: each of them is a critical part of the hybrid cloud business case. A hybrid cloud should not have large operational barriers to entry, such as having to create new apps, making large upfront investments in isolated public cloud infrastructure, or locking an enterprise in to a single vendor.
A hybrid cloud operating model brings new capabilities, with substantial business impact. It allows enterprises the flexibility and freedom to run applications where and when most suitable.
If you would like to try the hybrid cloud, check us out. For a limited time we are offering free beta trials of our cloud migration solutions.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)