Cloud Computing Terminology: A Complete Glossary
Cloud computing comes with its own dense vocabulary, and terms like IaaS, SaaS, and elasticity get thrown around constantly without much explanation. If you also need the deployment model side of the picture, our guide to cloud deployment models and characteristics covers that separately. This glossary breaks down the terminology that matters most, in plain language, so the jargon stops being a barrier to understanding.
Cloud Computing
The on-demand delivery of computing resources, servers, storage, databases, networking, and software, over the internet, with pricing typically based on actual usage rather than a fixed upfront investment in hardware.
SaaS (Software as a Service)
Fully managed software applications delivered over the internet, where the provider handles everything from infrastructure to updates. Gmail, Salesforce, and Dropbox are common examples. The user simply logs in and uses the software.
PaaS (Platform as a Service)
A managed platform that gives developers the tools to build, test, and deploy applications without managing the underlying servers or operating systems. Heroku and Google App Engine are well-known examples.
IaaS (Infrastructure as a Service)
Raw computing infrastructure, virtual machines, storage, and networking, rented from a provider, giving the most control but also the most responsibility for configuration and maintenance. AWS EC2 and Azure Virtual Machines are typical examples.
The Difference Between SaaS and “the Cloud” Generally
People often use “the cloud” and “SaaS” interchangeably, but SaaS is just one category within the broader cloud computing umbrella. The cloud also includes IaaS and PaaS, which involve much more technical setup than simply logging into a ready-made application. If you have ever used Google Docs without installing any software, you have used SaaS specifically, which is a subset of cloud computing as a whole.
Elasticity
The ability of a cloud system to automatically scale computing resources up or down based on real-time demand, so a website can handle a traffic spike without manual intervention and then scale back down once traffic normalises.
Provisioning
The process of setting up and allocating cloud resources, such as a virtual server or a storage volume, so they are ready for use. Modern cloud provisioning is typically automated and can happen in seconds rather than the days or weeks required for physical hardware.
Multi-Tenancy
An architecture where a single instance of software or infrastructure serves multiple customers, or “tenants,” while keeping each customer’s data logically separated and secure from the others.
Cloud-Native
Applications specifically designed to take advantage of cloud computing’s strengths, such as scalability and resilience, from the ground up, typically built using containers and microservices rather than adapted from older, traditional software architectures.
Containers
Lightweight, portable packages that bundle an application together with everything it needs to run, so it behaves consistently whether deployed on a developer’s laptop or a cloud provider’s servers. Docker is the most widely used container technology.
Orchestration
The automated management of containerised applications across a cluster of machines, handling tasks like scaling, load balancing, and recovering from failures. Kubernetes is the dominant orchestration tool in this space.
Availability Zone
A physically separate data centre within a cloud provider’s larger geographic region, designed so that a failure in one zone does not take down services running in another zone within the same region.
Cloud Operating System
A somewhat informal term referring to the software layer that manages and coordinates cloud resources, such as compute, storage, and networking, across a data centre, rather than a traditional operating system installed on a single device. OpenStack is a commonly cited example of open-source cloud operating system software.
Shared Responsibility Model
The division of security duties between a cloud provider and its customer: the provider secures the underlying infrastructure, while the customer is responsible for correctly configuring their own applications, data, and access controls on top of it.
Vendor Lock-In
The difficulty and cost involved in switching from one cloud provider to another, often caused by reliance on that provider’s proprietary tools, APIs, or data formats that are not easily portable elsewhere.
Latency
The delay between a user’s request and the cloud system’s response, typically measured in milliseconds. Lower latency generally means a faster, more responsive application, and is heavily influenced by the physical distance to the nearest data centre.
Uptime / SLA (Service Level Agreement)
Uptime refers to the percentage of time a cloud service is operational and accessible. An SLA is the formal contract in which a provider commits to a specific uptime guarantee, such as 99.9%, along with the compensation offered if that target is not met.
Quick Reference Table
| Term | One-Line Definition |
| SaaS | Ready-to-use software over the internet |
| PaaS | Managed platform for building applications |
| IaaS | Raw rented infrastructure (servers, storage) |
| Elasticity | Auto-scaling resources up or down with demand |
| Multi-tenancy | One system serving multiple isolated customers |
| Cloud-native | Built specifically to run well in the cloud |
| Orchestration | Automated management of containerised apps |
Frequently Asked Questions
What is the difference between SaaS and cloud computing?
SaaS is one specific category of cloud computing, ready-made software delivered over the internet. Cloud computing is the broader umbrella term that also includes IaaS and PaaS, which involve much more infrastructure-level control.
Is a cloud operating system the same as Windows or macOS?
No. A cloud operating system manages resources across a data centre or cluster of machines, while Windows or macOS manages resources on a single personal device.
Conclusion
Cloud computing terminology can feel dense at first, but most of it builds on a small set of core ideas: on-demand access, shared infrastructure, and automated scaling. Once these terms click, the rest of the vocabulary tends to make sense quickly.