The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Cloud computing did not begin with one invention or a single launch date. It developed from earlier ideas about sharing computer time, advances in networking, web-based software, and services that let customers provision storage and computing capacity over the internet. The 1960s supplied important precursors; modern public cloud services took shape much later.
What is the history of cloud computing?
The history is best understood as several related developments converging. First, organizations explored ways for multiple people to share costly computers. Networking then made remote access increasingly practical. Web applications delivered software over the internet, while later services made storage and computing infrastructure available on demand.
These stages are connected, but they are not interchangeable. Shared processor time is not the same thing as a self-service cloud platform, and a web application is not the same service as rented computing infrastructure.
When did cloud computing start?
There is no single start date established by this historical record. The 1960s are a period of precursors and proposals, not the beginning of cloud services in the modern sense. A 2011 U.S. congressional hearing record describes time-sharing and utility-computing ideas from that decade, later grid computing, and commercial development during the 2000s. It presents cloud computing as evolutionary rather than the product of one decisive invention. Read the hearing record.
Recommended Free Tools
#1 Best Overall
Google Cloud’s retrospective points to multi-user operating systems in 1967 and ARPANET’s introduction in 1969 as foundations for networked computing. It also describes the World Wide Web as a step toward making network computing accessible to mass audiences, followed by cluster-based internet services and cloud computing. That is a useful vendor-authored account of technical context, not a neutral or exhaustive chronology. Google Cloud’s cloud-computing overview.
How did web software and cloud infrastructure develop?
Web-delivered software
One strand of the story is software delivered through a browser or network rather than installed and maintained entirely on each user’s computer. A Stanford course-slide excerpt lists Salesforce in 1999 as an early software-as-a-service milestone. This is a signpost in a secondary timeline, not independent primary documentation of Salesforce’s launch. Stanford’s cloud-computing course excerpt.
On-demand storage and computing
A distinct strand is infrastructure that customers can obtain remotely instead of buying and operating all of it themselves. AWS says Amazon S3 launched in 2006 for remote storage, followed a few months later by Amazon EC2, which provided computing capacity. AWS describes these services as a breakthrough in IT infrastructure; that characterization is the company’s own framing. AWS’s account of its origins.
The difference matters: a hosted software application gives users a finished service, while infrastructure services let customers provision building blocks such as storage or compute. The 2006 S3 and EC2 launches are useful milestones in the shift toward remotely provisioned infrastructure, not proof that cloud computing suddenly appeared that year.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
What does NIST’s definition add to the timeline?
As cloud services developed, a shared vocabulary became useful for describing what counted as cloud computing and comparing different offerings. In September 2011, the National Institute of Standards and Technology published SP 800-145, authored by Peter Mell and Tim Grance. NIST defines cloud computing as “a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.” NIST SP 800-145.
The framework identifies five essential characteristics, three service models, and four deployment models. In its October 2011 account, NIST said the definition’s first draft was created in November 2009 and that it went through 15 drafts before the final, 16th version; the final text remained substantively similar to the draft. NIST computer scientist Peter Mell said the definition gives agencies and companies a tool for assessing whether implementations meet the cloud characteristics and models. NIST’s 2011 announcement.
Five characteristics
- On-demand self-service: users can provision capabilities as needed without requiring each action to be handled manually by the provider.
- Broad network access: capabilities are available over a network through standard access mechanisms.
- Resource pooling: provider resources serve multiple customers, with resources assigned and reassigned as demand changes.
- Rapid elasticity: capabilities can be scaled up or down quickly in response to demand.
- Measured service: resource use is monitored, controlled, and reported, supporting transparency for provider and customer.
Service models
- Software as a Service (SaaS): the customer uses the provider’s application.
- Platform as a Service (PaaS): the customer deploys applications using the provider’s supported environment.
- Infrastructure as a Service (IaaS): the customer provisions fundamental computing resources such as processing, storage, or networks.
Deployment models
- Private cloud: cloud infrastructure for the exclusive use of one organization.
- Community cloud: infrastructure shared by organizations with common concerns.
- Public cloud: infrastructure made available for open use by the general public.
- Hybrid cloud: two or more distinct cloud infrastructures connected to enable data or application portability.
How did cloud computing scale after its early services?
As use grew, cloud computing came to involve large clusters of machines, high-speed networks, and services operating at very large scale. Google Cloud’s retrospective describes this as a move toward warehouse-scale clusters and “planet-scale” services. This perspective helps explain the technical context of later cloud systems, but it is one provider’s account rather than a complete history of every company or development. Google Cloud’s overview.
Who invented cloud computing?
No single inventor is established by these milestones. The history spans earlier sharing and utility-computing ideas, networking, web software, commercial infrastructure services, and later standardization. It is more accurate to describe cloud computing as a cumulative evolution than to credit one person with inventing the modern model.
How to distinguish the major milestones
| Milestone | What was shared or delivered | How it reached users | What changed |
|---|---|---|---|
| 1960s time-sharing and utility-computing ideas | Access to computing resources, including processor time | Time-sharing and networked access concepts | More than one user could make use of costly computing resources; this was a precursor, not today’s public cloud model. |
| Network foundations, including ARPANET in 1969 | Communication between networked computers | Computer networks | Remote connectivity laid groundwork for later network services. |
| Salesforce listed in 1999 as an early SaaS milestone | Software | Web-delivered application | Users could access software as a service rather than treating it solely as locally installed software. |
| Amazon S3 and EC2 in 2006, according to AWS | Remote storage and computing capacity | On-demand services over the internet | Customers could obtain infrastructure resources remotely; AWS calls the services a breakthrough in IT infrastructure. |
| NIST SP 800-145 in 2011 | A definition and classification framework | Published standard | Organizations gained shared characteristics and models for describing and comparing cloud implementations. |
The milestones do not all represent the same kind of change: some concern access to shared computers, others the delivery of software, infrastructure provisioning, or a formal definition. Keeping those distinctions clear makes the history easier to follow without treating every networked service as cloud computing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
