Cisco Cisco Intelligent Automation for Cloud 4.3.1 White Paper
For InFrastructure & operatIons proFessIonals
the Forrester Wave™: private cloud solutions, Q4 2013
18
© 2013, Forrester Research, Inc. Reproduction Prohibited
November 25, 2013
OpenStack-based solutions from Morphlabs, Piston Cloud, Cloudscaling, or Rackspace Cloud Builders.
They aren’t choosing solutions built from the virtualization layer up or built to preserve the traditional
enterprise IT management tools that are in place today. It’s not that solutions built from the latter aren’t
fully capable of being clouds, just that developers don’t know these vendors and don’t see their solutions
as aligned with the public clouds with which they want to integrate. The new cloud administrators are
starting fresh with new solutions that are designed to integrate with the public cloud first and the rest of the
enterprise second. For more information on traditional and cloud native applications, see the February 21,
fully capable of being clouds, just that developers don’t know these vendors and don’t see their solutions
as aligned with the public clouds with which they want to integrate. The new cloud administrators are
starting fresh with new solutions that are designed to integrate with the public cloud first and the rest of the
enterprise second. For more information on traditional and cloud native applications, see the February 21,
2013, “
” report.
13
Traditional enterprise applications and cloud-native applications differ in design and requirements.
Generally, applications that sit atop VMware vSphere are traditional Windows and Linux applications that
live within a static configuration of resources. They don’t scale out, they aren’t componentized web services,
and they tend to have a fixed and permanent footprint. And these applications never get turned off (at least
not on purpose). They were most likely built and configured for purpose and, in most cases, were put into
and they tend to have a fixed and permanent footprint. And these applications never get turned off (at least
not on purpose). They were most likely built and configured for purpose and, in most cases, were put into
virtual machines (VMs) that mimicked the physical server configuration they ran on. Cloud native apps
are elastic or transient. The best-fit applications in the cloud are designed to scale out, are componentized
in construction, intercommunicate via web services, and are designed to fail. They are optimized for cloud
environments and built under the assumption that they will run on commodity infrastructure and activate
cloud economics. Clouds encourage developers to adapt to their capabilities and services, which are highly
standardized, as they are shared among many customers. For more information on traditional and cloud
native applications, see the February 21, 2013, “
in construction, intercommunicate via web services, and are designed to fail. They are optimized for cloud
environments and built under the assumption that they will run on commodity infrastructure and activate
cloud economics. Clouds encourage developers to adapt to their capabilities and services, which are highly
standardized, as they are shared among many customers. For more information on traditional and cloud
native applications, see the February 21, 2013, “
” report.