EWEEK recently featured an interview with Adam Selipsky, the vice president of Amazon Web Services (AWS), in which he revealed the most persistent myths about cloud computing that he has to deal with in his job.
He cited five recurring myths about cloud adoption:
His answers to the first two objections are in-depth and compelling, outlining the considerable lengths that AWS takes to ensure both reliability and security.
He goes on to state that there is a psychological barrier, as CIOs can be under huge pressure to deliver performance from several thousand applications.
Traditionally, they felt comfortable knowing that if there were problems with an application, they could walk down the hall and collar the right person until it was fixed. Relinquishing that immediate control can be a leap of faith. “People think if they can control it they have more say in how things go. It’s like being in a car versus an airplane, but you’re much safer in a plane.” Mr Selipsky says.
He then moves on to the flaws in private clouds: They fail to eliminate CapEx, do not benefit from the efficiencies of multi-tenant resource allocation, do not benefit from the economies of scale of a public cloud, and do not allow the IT department to refocus on differentiating problems.
The fallacy of a complete and instantaneous switch to the cloud is quickly pointed out, leaving us with the final myth, that the biggest driver of cloud adoption is cost.
According to Rob Chapman, We Are Cloud, this is one he experiences over and over again. He has seen it written on many forums that cloud computing is at base glorified and well-marketed outsourcing. He argues that this is simply not true for 99 percent of cloud users. Part of its function is indeed outsourcing – tasks through which your company are not gaining a competitive advantage are taken off your hands – but cloud computing and SaaS bring so much more to the table.
This slideshow highlights the eight truths of the SaaS value proposition as outlined by Chapman.
Clearly the business of doing business is not simple, and if we are to achieve any measure of success by applying GRC across the board, we need technology. ... More >>
With pressure mounting to meet new regulatory requirements and ICD-10 deadlines, health care CIOs need a set of "best practices" to help them navigate this IT transformation and arrive at the data-driven, value-based future of health care. ... More >>
Building a federated GRC capability involves understanding the information architecture and processes that are critical to improving business performance, lowering risk exposure, and ensuring compliance with policies and regulations across the entire organization and its vendor communities. ... More >>