I really enjoyed reading the "10 Reasons Enterprises Aren’t Ready to Trust the Cloud " post from Stacey Higginbotham. She highlights some very important points in here analysis.
She outlines the following challenges with the cloud:
1. It’s not secure. We live in an age in which 41 percent of companies employ someone to read their workers’ email. Certain companies and industries have to maintain strict watch on their data at all times, either because they’re regulated by laws such as HIPAA, Gramm-Leach Bliley Act or because they’re super paranoid, which means sending that data outside company firewalls isn’t going to happen. 2. It can’t be logged. Tied closely to fears of security are fears that putting certain data in the cloud makes it hard to log for compliance purposes. While there are currently some technical ways around this, and undoubtedly startups out there waiting to launch their own products that make it possible to log “conversations” between virtualized servers sitting in the cloud, it’s still early days. 3. It’s not platform agnostic. Most clouds force participants to rely on a single platform or host only one type of product. Amazon Web Services is built on the LAMP stack, Google Apps Engine locks users into proprietary formats, and Windows lovers out there have GoGrid for supporting computing offered by the ServePath guys. If you need to support multiple platforms, as most enterprises do, then you’re looking at multiple clouds. That can be a nightmare to manage. 4. Reliability is still an issue. Earlier this year Amazon’s S3 service went down, and while the entire system may not crash, Mosso experiences “rolling brownouts” of some services that can effect users. Even inside an enterprise, data centers or servers go down, but generally the communication around such outages is better and in many cases, fail-over options exist. Amazon is taking steps toward providing (pricey) information and support, but it’s far more comforting to have a company-paid IT guy on which to rely. 5. Portability isn’t seamless. As all-encompassing as it may seem, the so-called “cloud” is in fact made of up several clouds, and getting your data from one to another isn’t as easy as IT managers would like. This ties to platform issues, which can leave data in a format that few or no other cloud accepts, and also reflects the bandwidth costs associated with moving data from one cloud to another. 6. It’s not environmentally sustainable. As a recent article in The Economist pointed out, the emergence of cloud computing isn’t as ethereal as is might seem. The computers are still sucking down megawatts of power at an ever-increasing rate, and not all clouds are built to the best energy-efficiency standards. Moving data center operations to the cloud and off corporate balance sheets is kind of like chucking your garbage into a landfill rather than your yard. The problem is still there but you no longer have to look at it. A company still pay for the poor energy efficiency, but if we assume that corporations are going to try to be more accountable with regard to their environmental impact, controlling IT’s energy efficiency is important. 7. Cloud computing still has to exist on physical servers. As nebulous as cloud computing seems, the data still resides on servers around the world, and the physical location of those servers is important under many nation’s laws. For example, Canada is concerned about its public sector projects being hosted on U.S.-based servers because under the U.S. Patriot Act, it could be accessed by the U.S. government. 8. The need for speed still reigns at some firms. Putting data in the cloud means accepting the latency inherent in transmitting data across the country and the wait as corporate users ping the cloud and wait for a response. Ways around this problem exist with offline syncing, such as what Microsoft Live Mesh offers, but it’s still a roadblock to wider adoption. 9. Large companies already have an internal cloud. Many big firms have internal IT shops that act as a cloud to the multiple divisions under the corporate umbrella. Not only do these internal shops have the benefit of being within company firewalls, but they generally work hard — from a cost perspective — to stay competitive with outside cloud resources, making the case for sending computing to the cloud weak. 10. Bureaucracy will cause the transition to take longer than building replacement housing in New Orleans. Big companies are conservative, and transitions in computing can take years to implement. A good example is the challenge HP faced when trying to consolidate its data center operations. Employees were using over 6,000 applications and many resisted streamlining of any sort. Plus, internal IT managers may fight the outsourcing of their livelihoods to the cloud, using the reasons listed above.
Many of these are excellent points and are valid issues. I faced these challenges before joining Microsoft. Back then we didn't call it "Cloud" or "S+S" though, back then it was ASP or Managed Services (pre-cloud). Even though they were called by different names many of the technology and operational challenges remained the same.
There was a promise that by moving applications to the cloud it will reduce the complexity in your enterprise. While this is true for some areas such as development, maintenance of application logic and application infrastructure logistics other operational, security and business related complexities increase. The question becomes, is there more, less or the same amount of complexity as the pendulum swings to the other side?
With the uncertainty of the answers to such questions many enterprises are reluctant to “trust” the cloud. However, with challenges there is an opportunity for Cloud based services to provide enterprise ready Cloud services.
コメント