Here is a collection of thoughts I pulled together from recent conversations with colleagues and customers about what constitutes a "cloud solution" or whether an application is a "cloud application.” I'd love to have some comments on this.
I have been working on use cases for one aspect of the cloud, storage (besides backup). There are four that seem to make sense. Can anyone think of anything else?
- Geographic dispersal
- Data stored on low cost media
- Apply WORM policy for compliance
- Web Content
- Content stored on low cost media
- Use polices to position data
- Users access data directly
- Disaster Recovery
- Replicate Data into the Cloud
- Apply polices to geographically disperse data
- Production data can be recalled when disaster strikes
- Dynamic Data Allocation
- Directed at dynamic content such as video and delayed live feed
- Data replicated in geo-specific clouds (i.e. NA, SA, EU, Africa)
- Rapid rollout and tear down required
Some other thoughts from a recent presentation I made:
- Remember principles of data management
- Cloud Storage works when
- Performance is not an issue
- Capacity is needed
- It fits the workflow
- Cheap storage is easy; we all can do this, but…
- Geographically replicated, efficiently managed, AND cheap?
- A useful archive or deep storage tier
- Data mining & re-analysis done in-situ with local cloud server resources if needed
- “Downloader pays” good model to offset costs
Is the Cloud "Right" For You?
As we (data storage architects) attempt to design and implement solutions, we are trying to solve a customer’s business problems while setting them up with a foundation for “smart growth” in technology. We should be thinking about these questions:
1. Will the customer benefit from a self-provisioning architecture that allows business users to set up their own servers/applications/storage/networking, and does that make sense from a business perspective?
2. Will the customer’s business benefit from IT that grows and shrinks in performance and capacity as needed?
3. Will the business benefit from “pay for use” by the end user as a way to track investment and IT resource utilization?
4. Does the customer need to allow access to its business from anywhere, at any time?
5. Should the customer IT infrastructure be rebuilt so that it consists of “pools” of virtualized computing, networking and storage; and does that make sense from a business perspective?
The answers to these questions are not always “Yes.” Most companies do not need to build a private cloud now, or in the immediate future, but they need to understand what these changes could mean to them, both as IT professionals and as business enablers.
By Who and When Will the Cloud be Adopted?
As has been pointed out by others, adoption of cloud-like computing will likely take place within IT and at the consumer and small-business level first, although latency issues will remain for business computing in the public cloud until the technology finishes maturing and content can be made ubiquitous (cheaply pushed out to the edge where it is needed). IT staff at larger companies will want cloud-like computing in the datacenter to ease power and space crunches and make them more efficient with a self-provisioning, elastic, network-based infrastructure. However, as EMC has noted, it is a bit harder to push the enterprise business applications into a cloud. That will come with time, as power, cooling and staffing resources force efficiency on small business and datacenters alike. It will be enabled by the successes we can make happen now and as the “hump” of the bell curve moves closer to the elastic infrastructure and virtualized computing environment we now call the Cloud.
The Litmus Test
Ask yourself if any technology fits most or all of these requirements. If not, it is not a cloud technology.
• Self provisioning?
• Pay as you go?
• Pooled resources?
• Ubiquitous network access?
SharePoint would be a great application to have in the cloud, but the resource pooling and provisioning would be infrastructure based, and that is where the cloud technology surfaces. A service provider could allow you to request what is needed to deploy or scale SharePoint, but what is the technology behind the portal? BMC? Surgient? Something else? What is the storage behind it? How will the content and computing be geographically dispersed so that latency won’t be an issue?
I think any web-based interface to an application can be considered “enabling,” since that meets the “ubiquitous access” criteria. What will it be used for? How will it enable self-provisioning? Is what is being done through the interface able to scale?
Ask Yourself This:
It all comes back to the same thing…what are you moving (and why) from the old paradigm of datacenter computing to the new paradigm, regardless of whether it is private, public or federated?