Cloud Computing

Cloud computing provides computing resources and software over a network from shared, configurable systems that can be provisioned on demand. Its common service models—software, platform and infrastructure as a service—and deployment models—public, private, community and hybrid—describe different ways to deliver and manage those resources. Elastic capacity can be useful, but cost, security, reliability and data portability depend on the workload and service arrangement.

Last updated
17 October 2026
Confidence
High (96%)
Sources
5
Versions
1
This article was researched and drafted with AI assistance and checked by an automated review pass. It is not guaranteed to be accurate — verify important facts against the references below.

Definition and characteristics

Cloud computing is a way to make computing capabilities—such as processing, storage, networks, applications and other services—available over a network from a shared pool of configurable resources. Instead of acquiring and operating every computer locally, a user can request resources from a provider and access them remotely.

A widely used National Institute of Standards and Technology (NIST) framework describes five defining characteristics: users can provision resources on demand; services are reachable over networks; providers pool resources among customers; capacity can expand or contract rapidly; and resource use is metered. These features distinguish cloud computing from simply running a computer remotely or storing a file on a network.

Service models

NIST groups cloud services into three broad models. Software as a service (SaaS) gives customers access to an application operated by a provider, usually through a browser or program interface. Platform as a service (PaaS) provides an environment for customers to deploy applications while the provider manages the underlying infrastructure. Infrastructure as a service (IaaS) supplies fundamental resources such as processing, storage and networking, allowing customers greater control over operating systems and applications.

The models differ mainly in which parts of the computing stack the provider operates and which remain the customer's responsibility. In practice, products may combine services or draw boundaries differently, so a label alone does not describe every responsibility or guarantee.

Deployment models and infrastructure

Deployment models describe who the cloud environment is intended for and how it is organized. A public cloud is available for general use; a private cloud is reserved for one organization; a community cloud is reserved for organizations with shared concerns; and a hybrid cloud connects two or more distinct cloud infrastructures. Ownership and operation can vary, particularly for private and community clouds.

Cloud services run on data-centre infrastructure. Virtualization and related software can divide physical computing resources into separate virtual environments, while management systems allocate and measure capacity. Resource pooling can make it easier to serve changing demand, although the customer may have limited knowledge of the exact physical location of a resource.

Benefits and trade-offs

Elastic provisioning can help an organization respond to unpredictable or fluctuating workloads without buying enough equipment to handle every possible peak. Usage-based arrangements may also reduce the need for a large initial investment. These advantages are not automatic: whether cloud use is economical depends on utilization, pricing, data-transfer needs, migration work and the level of management the customer still performs. Moving a workload can also create dependence on a provider's interfaces or make data and applications harder to move elsewhere.

Cloud adoption therefore involves trade-offs among flexibility, control, portability, performance and cost. A service that works well for a variable web workload may not be the best choice for every application or organization.

Security and governance

Storing or processing information on infrastructure operated by another organization raises questions about confidentiality, integrity, availability, data location and access. Security depends on the chosen service and deployment model, technical controls, contracts and how both provider and customer carry out their responsibilities; using a cloud does not by itself make information secure or insecure. Portability and continuity plans also matter if a provider changes its service or becomes unavailable.

In a 2026 review of selected U.S. federal cloud systems, the Government Accountability Office found that agencies varied in implementing key practices, including continuous monitoring and service-level agreements. The review concerned a limited set of systems, but illustrates why organizations must assess controls and service commitments rather than assume that outsourcing removes their oversight obligations.

Historical development

Cloud computing grew from the broader idea of computing as a utility and from earlier attempts to deliver applications remotely. Encyclopaedia Britannica describes application service providers that emerged in the late 1990s and notes that remote application delivery became more popular under the cloud-computing label about a decade later. The later combination of network access, large data centres, virtualization and on-demand provisioning made it practical to offer computing resources as services at scale. There is no single event that marks the invention of cloud computing; the term covers a set of related technologies and delivery models.

Key facts

Core idea
Network access to a shared pool of configurable computing resources.
NIST characteristics
On-demand self-service, broad network access, resource pooling, rapid elasticity and measured service.
Service models
Software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS).
Deployment models
Public, private, community and hybrid clouds.
Key trade-offs
Flexibility and elastic capacity must be weighed against cost, security, reliability, performance and portability.

Timeline

  1. Late 1990s

    Application service providers began supplying applications to organizations over the Internet, an earlier form of remote application delivery.

  2. 2006

    The Berkeley researchers identify Amazon Web Services' introduction of pay-as-you-go computing as an important step in the commercial development of cloud services.

  3. September 2011

    NIST published Special Publication 800-145, setting out a definition and taxonomy for cloud computing.

Ask about this article

Answers use only “Cloud Computing” and its references, with citations.

References

  1. 1.
    The NIST Definition of Cloud Computing

    National Institute of Standards and Technology, U.S. Department of Commerce · other · reliability: high · retrieved 17 October 2026

    Supports: Defines cloud computing and its five essential characteristics, three service models and four deployment models.

  2. 2.
    Cloud computing Security, Cost Savings & Flexibility

    Encyclopaedia Britannica · other · reliability: high · retrieved 17 October 2026

    Supports: Overview of cloud services, data centres, virtualization, privacy concerns and the historical development of remote application services.

  3. 3.
    Above the Clouds: A Berkeley View of Cloud Computing

    University of California, Berkeley, Electrical Engineering and Computer Sciences, Technical Report UCB/EECS-2009-28 · other · reliability: high · retrieved 17 October 2026

    Supports: Research analysis of cloud computing's utility model, elasticity, economic trade-offs and adoption obstacles, including availability, data lock-in and security.

  4. 4.
    A View of Cloud Computing

    Communications of the ACM, Association for Computing Machinery · other · reliability: high · retrieved 17 October 2026

    Supports: Explains cloud service delivery and discusses workload elasticity, usage-based pricing, outages, data portability and security concerns.

  5. 5.
    Cybersecurity: Selected Agencies Need to Better Protect Cloud Data

    U.S. Government Accountability Office · other · reliability: high · retrieved 17 October 2026

    Supports: A 2026 review of selected federal cloud systems found variation in implementation of monitoring and service-agreement security practices.

References are suggested by the research engine and may be incomplete. Unverified URLs are omitted rather than guessed.

Article history

  1. Version 117 October 2026 · EditorCreated by Zapia