The cloud is well on its way to becoming the standard model for IT, just 16 years after it first formed. It couples flexibility, scale, and reliability to user-friendliness and ubiquity. It has created some of the world’s largest companies, as well as empowering some of the smallest. The cloud has changed the economics of providing and using services, bringing many new opportunities—and also a few teething problems of course.
Here in the British Isles, clouds are notorious for obscuring the view, but you might be surprised to learn that the technological underpinnings of cloud computing are now transparent, mature, and mostly based on open-source tech. The new, cloudy landscape is growing increasingly clear. For the first time, it’s now possible to see the nature and usage of private, public, and hybrid clouds and explore their respective strengths, weaknesses, and applicability.
Condensation nuclei
The foundations of the cloud were laid half a century ago. Books like "The Challenge of the Computer Utility" by Douglas F. Parkhill, published in 1966, noted that computers were getting powerful enough to provide information and services at scale to ordinary people, but that the machinery was so big and expensive that it would have to be remotely accessed. Utility computing was so named because it saw computing becoming as universal as power and water, delivered on demand and charged for in much the same way. In particular, people would no more need to run their own computing systems as they would own their own power generators or drill their own wells.
At the same time, two other fundamental drivers for the cloud began to condense. Future Intel co-founder Gordon Moore coined his eponymous law, saying in effect that integrated circuit technology would double computing power every two years or so. Meanwhile, Paul Baran at the RAND Corporation in the US and Donald Davies at the UK’s National Physical Laboratory independently invented packet switched networking—a much more robust, efficient, and flexible way of moving data through a common infrastructure than permanent connections of telephone-style switched circuits could manage.
In the 1970s, Ken Thompson and Dennis Ritchie at Bell Labs led the creation of Unix and the C programming language—the first credible pieces of system software designed to be easily run on a variety of platforms. Combined with open networking standards developed for ARPANET by Vint Cerf, Bob Kahn, and friends, the lining of the cloud had begun to coalesce in earnest.
Over the next two decades, the invention and popularisation of DSL (another Bell Labs marvel) and the mass-market success of Windows 95 (which supported TCP/IP) spurred the arrival of commercial ISPs, while early deployments of grid computing and application service providers (ASPs) showcased the benefits that might be had from cloud-like thinking.
Then, quite suddenly at the end of the 20th century, everything clicked into place. The technology was just about there, and the economies of scale provided by data centres were once again returning the advantage to large, centralised computing. It was time to go… to the cloud!
First men in the clouds
The modern cloud appeared in the shape of Salesforce.com in 1999. It sold a pure business service: customer relationship management. CRM is exactly what it sounds like. A company uses a CRM to keep track of who it’s selling to, what it’s sold, and how to keep everyone happy. Before Salesforce.com, companies bought or wrote CRM software and ran it on their own computers. Salesforce wrote CRM software, but instead of delivering copies of it to customers, it ran it on its own data centre and sold per-user access to it. The software never left the building, and its customers didn’t have to do anything more than point their Web browsers at the Salesforce.com site, set up an account, log in, and start working.
This seems entirely normal now that using Gmail seems more natural than running Outlook on your PC. Yet Salesforce.com was revolutionary when it arrived, eight years before Gmail. In the years since, the cloud has engulfed the planet.
Cloud atlas
Clouds are simple things at heart, but they come in different shapes. Gmail, Salesforce.com, and anything you run via your Web browser is called SaaS—Software as a Service, and it’s what most users think of as “the cloud.” There are two other acronyms that often crop up to describe different cloud formations: Platform as a Service (PaaS) and Infrastructure as a Service (IaaS). Of interest primarily to people who have to build IT for other people, these roughly equate to having a cloud that will run your own application software (PaaS) or having what looks like bare hardware you can do what you like with (IaaS). Amazon Web Services (AWS) and Rackspace are good examples of IaaS; Google App Engine of PaaS.
Some companies, such as HP, IBM, and Microsoft (Azure), provide a mix of both IaaS and PaaS. Religious wars rage over exactly where the boundaries lie, but neither acronym really describes the way that the cloud is evolving into a general set of services designed for other software to use. These developments can be clearly seen if you look at the recent rapid evolution of mobile technology, which is itself largely the product of the first cloud-hosted services.
"Cloud has been one of the most significant enablers for the advancement of the mobile platform," Brian Levine, senior director of security and compliance at cloud storage services company Syncplicity, told Ars Technica in an interview. "Without cloud as the first wave, we would not have seen the second wave in the explosion of mobile applications and services. Facebook, Instagram, Snapchat, WhatsApp; none of these applications would exist without the cloud layer. On mobile, you essentially have a window into the cloud, and very little storage and computing occurs on the device. Most of the mobile processing happens in the cloud."
SaaS and mobile data-sharing apps are how most of us experience the public cloud, which was the first and remains the largest aspect of cloud computing. Salesforce.com runs everything, stores everything, controls everything. Its users can be anyone and everyone, and they have absolutely nothing to maintain except Web browsers and an Internet connection. They pay for what they use of the service and don’t have to pay for specialist IT staff, infrastructure, software updates, and so on.
There are also private clouds, where companies use some of the techniques and technologies of the public cloud but run it all themselves behind closed doors. Cloud systems are designed to be very quick to grow and very good at distributing data to lots of people with little effort—areas where traditional corporate IT has rarely covered itself with glory. With the private cloud, everything runs centrally and is accessed through a Web browser rather than being copied onto desktops. As a result, employees get a familiar browser-based environment to work in, and, when you run everything yourself, it’s easier to connect up older, legacy software systems that simply don’t have equivalents in the public cloud. Whatever the reasons, the private cloud remains in many respects similar to the old-style company IT approach of locked-down, controlled fiefdoms.
Some see the private cloud as a benign Trojan horse, bringing some of the more revolutionary aspects of the public cloud into the rather conservative world of enterprise IT. Those old enough to remember when software came on CDs will also remember that bug fixes and new versions came fitfully at best, and if you didn’t like something you were stuck with it. That’s not the modern experience, especially on mobile platforms, where updates are seamless and usability constantly tuned. The ability of cloud-based systems to update very quickly and at scale has become a necessity.
"Today, what needs to be understood is that in traditional IT, when you had an application, you were developing a new release of this application once or twice a year—but not more." Xavier Poisson, vice president of cloud computing for EMEA at HP, told Ars. "With mobility and the need to be more agile, you’ve got to have a completely new development cycle, and it’s essential to develop more quickly."
A vigorous hybrid
While the private cloud may bring these ideas within the corporate comfort zone, in practice the most common model is a mix of public cloud and private infrastructure: the hybrid cloud. This is more a term of convenience than a single technology; it’s when a company does some IT in-house, and some in the public cloud; it covers everything from running Gmail alongside a local copy of Microsoft Office, to running development versions of your global share trading platform in your R&D bunker before pushing it out to a hundred-server cluster on Microsoft Azure.
The increasing use of hybrid cloud tech is a reflection of the economic drivers that pull more and more IT, corporate and consumer, towards the public cloud. The most fundamental driver is good old economy of scale. When a public cloud company buys hardware, they pay a lot less than you do, whether you are Josephine Bloggs at home or a large retailer running a respectable data centre.
Cloud providers find it very distasteful to talk about their money, but in 2009 researchers at Berkeley University estimated that economy of scale meant that large cloud providers were paying between one-third and one-seventh as much for their networking, hardware, and power as companies did for their internal IT. With cloud providers growing at around 50 percent per year since then, that disparity is now much greater—and explains why, as research group Baird says, companies save three to four dollars on internal IT for every dollar they spend on shifting infrastructure and services to cloud.
reader comments
222