Caleb Whitaker
The Droven.io Cloud Computing Guide to key concepts and terms exists for a simple reason: cloud computing has a vocabulary that can feel like a second language. IaaS, availability zone, egress fee, and container get tossed around as if everyone was born knowing them. This article defines the ideas that matter most in plain English, so you can read a provider’s documentation or a vendor proposal without stopping every few lines to look something up.
The sections below move from the basic definition to service models, deployment options, technical building blocks, pricing, and security. Each section stands on its own, so you can jump to the term you need or read straight through.
What Is Cloud Computing?
Cloud computing is the delivery of computing resources, such as servers, storage, databases, networking, and software, over the internet on a pay-for-what-you-use basis. Instead of buying and maintaining your own hardware, you rent capacity from a provider that runs large data centers.
The definition most often cited comes from the U.S. National Institute of Standards and Technology (NIST). It describes cloud computing as a model for on-demand network access to a shared pool of configurable resources that can be provisioned with minimal management effort. The wording is dry, but it captures the two ideas that matter most: resources are shared, and you get them when you ask for them.
A common comparison is the difference between running your own generator and plugging into the power grid. The generator gives you control but demands fuel and upkeep. The grid delivers power on demand and sends a bill at the end of the month. The analogy is not perfect, since cloud services vary widely in complexity and pricing, but it explains why so many organizations made the switch.
The Five Essential Characteristics of Cloud Computing
NIST lists five characteristics that separate genuine cloud services from ordinary web hosting. They work as a handy test. If a service lacks most of them, it probably is not cloud in the strict sense.
- On-demand self-service: You can provision resources yourself through a web console or API, without filing a ticket or calling a salesperson.
- Broad network access: Services are reachable over the network from many kinds of devices, including laptops, phones, and other servers.
- Resource pooling: The provider serves many customers from a shared pool of hardware, an arrangement usually called multi-tenancy. Your data stays logically separated from everyone else’s.
- Rapid elasticity: Capacity can grow or shrink quickly, often automatically, as demand changes.
- Measured service: Usage is metered, which is what makes pay-as-you-go billing possible.
Once you can recognize these five traits, most cloud marketing language becomes easier to decode.
Cloud Service Models: IaaS, PaaS, and SaaS
Service models describe how much of the technology stack the provider manages for you. The more they handle, the less control you have, and the less work lands on your plate.
Infrastructure as a Service (IaaS)
IaaS gives you virtual machines, storage, and networking. You choose the operating system and manage everything above it, including patches, applications, and configuration. Amazon EC2, Microsoft Azure Virtual Machines, and Google Compute Engine are familiar examples. It is the closest thing to renting space in a data center without ever visiting one.
Platform as a Service (PaaS)
PaaS adds a managed runtime on top of the infrastructure. Developers push their code, and the platform takes care of servers, operating systems, and often scaling. Google App Engine, Azure App Service, and AWS Elastic Beanstalk fall into this group. It suits teams that want to ship applications without becoming part-time system administrators.
Software as a Service (SaaS)
SaaS delivers a finished application through a browser or app. Gmail, Microsoft 365, Salesforce, and Slack are typical examples. You manage your settings, users, and data, while the provider handles everything underneath. If you have ever used web-based email, you have used SaaS.
Serverless and Function as a Service
Serverless is a newer term and a slightly misleading one. Servers still exist, but you never manage or even see them. With function-as-a-service tools such as AWS Lambda, you upload a small piece of code that runs in response to an event, like a file upload or a web request. Billing follows execution rather than uptime, so idle code costs little or nothing.
Public, Private, Hybrid, and Multi-Cloud Deployment Models
Where the service model answers “what do I get,” the deployment model answers “who owns and shares the environment.”
Public cloud means the infrastructure is owned by a provider and shared among many customers. AWS, Microsoft Azure, and Google Cloud are the best-known examples. It is usually the fastest and cheapest way to start.
Private cloud means the environment is dedicated to a single organization. It might sit in the company’s own data center or be hosted by a third party. Organizations choose it for tighter control, specific compliance needs, or existing hardware investments.
Hybrid cloud connects a private environment with one or more public clouds so workloads can move between them or work together. A company might keep sensitive records on private systems while running its public website in the public cloud.
Multi-cloud means using services from more than one public cloud provider. People often confuse this with hybrid cloud. The difference is simple: hybrid mixes private and public, while multi-cloud combines multiple public providers. An organization can be both at once.
NIST also describes a community cloud, shared by several organizations with common concerns such as a regulatory requirement. It is far less common in everyday conversation.
Core Building Blocks: Compute, Storage, and Networking
Every cloud platform, no matter the brand, is built from the same three categories of resources.
Compute
Compute is the processing power that runs your applications. The traditional unit is the virtual machine (VM), a software-defined computer that runs on shared physical hardware. A hypervisor is the software that carves one physical server into many VMs.
Containers are a lighter alternative. They package an application with the files and libraries it needs, so it runs the same way on a laptop, a test server, or a production cluster. Kubernetes is a widely used open-source system for managing large numbers of containers, handling tasks like scheduling and restarting failed ones.
Storage
Cloud storage comes in three main types, and picking the wrong one is a common beginner mistake.
- Object storage holds files as discrete objects with metadata, and works well for backups, images, video, and static website files. Amazon S3 is the best-known example.
- Block storage behaves like a hard drive attached to a VM, and suits databases and operating systems that need fast, consistent performance.
- File storage offers a shared folder structure that multiple machines can access at once.
Networking and Geography
A virtual private cloud (VPC) is a logically isolated section of a provider’s network where you control IP ranges, subnets, and traffic rules. A load balancer spreads incoming requests across several servers so no single one gets overwhelmed. A content delivery network (CDN) caches copies of your content in many locations so users receive it from a nearby server.
Geography matters too. A region is a physical area, such as US East or Western Europe, where a provider operates data centers. An availability zone is a separate data center, or group of data centers, within a region, with independent power and networking. Spreading an application across zones protects it if one location fails.
Scalability, Elasticity, and High Availability: What Is the Difference?
These three words are often used as if they mean the same thing. They do not.
Scalability is the ability to handle more work by adding resources. You can scale vertically (a bigger server) or horizontally (more servers).
Elasticity is scalability that adjusts automatically, in both directions. A shopping site that adds servers during a sale and removes them afterward is behaving elastically.
High availability is about staying online when something breaks. It usually depends on redundancy, such as running copies of your application in multiple availability zones.
A related term, durability, describes how unlikely stored data is to be lost. It is not the same as availability. A file can be extremely durable yet temporarily unreachable during an outage.
Cloud Pricing Terms That Affect Your Bill
Cloud pricing is one of the areas where beginners get surprised, so these terms are worth learning early. Exact rates and discount programs differ by provider and change over time, so always check current pricing pages before making decisions.
- Pay-as-you-go: You pay for what you use, typically by the second, hour, or gigabyte, with no long-term commitment.
- Reserved or committed use: You promise to use a certain amount of capacity over a set period, often one or three years, in exchange for a lower rate.
- Spot or preemptible instances: You use spare provider capacity at a steep discount, with the catch that the provider can reclaim it on short notice. These suit workloads that can tolerate interruption.
- Egress fees: Charges for moving data out of a provider’s network. Uploading is usually free or cheap, while downloading or transferring elsewhere can add up.
- Free tier: Limited free usage that many providers offer to new users for learning and testing.
Managing these costs has become a discipline of its own, often called FinOps. Even a small team benefits from setting budgets and billing alerts on day one, since a forgotten test server can quietly run up charges.
Cloud Security Terms Worth Knowing
Security is where misunderstanding can be costly, so a few terms deserve careful attention.
The shared responsibility model is the most important one. In short, the provider secures the underlying cloud (physical facilities, hardware, and core services), and the customer secures what they put in it (data, configurations, access, and applications). The exact split shifts by service model. With SaaS, the provider covers more. With IaaS, you cover more.
Identity and access management (IAM) is the system that controls who can do what. A sound habit is the principle of least privilege, meaning every person and application receives only the permissions it needs.
Encryption at rest protects stored data, while encryption in transit protects data as it moves across networks. Most major providers support both, but you often need to confirm they are turned on and configured correctly.
You will also see compliance frameworks mentioned, such as SOC 2, ISO 27001, HIPAA, and GDPR. These are standards or regulations, and a provider’s certification does not automatically make your own setup compliant. Misconfiguration on the customer side is a frequent source of cloud security incidents, which is exactly why the shared responsibility model deserves your attention.
Cloud Terms People Commonly Confuse
A few pairs trip up newcomers again and again.
Virtualization versus cloud computing. Virtualization is a technology that lets one physical machine act as many. Cloud computing builds on it by adding self-service, pooling, metering, and automation. You can have virtualization without cloud, but not really the other way around.
Cloud storage versus backup. Syncing files to a cloud folder is not the same as having a backup. If you delete or corrupt a synced file, that change may spread everywhere. A real backup keeps separate, recoverable copies.
Region versus availability zone. A region is a broad geographic area. Zones are separate facilities inside it. Choosing a region affects latency and legal data location, while using multiple zones affects resilience.
SaaS versus cloud computing. SaaS is one service model within cloud computing, not a synonym for it.
How to Use This Guide to Build Cloud Skills
Reading definitions helps, but the vocabulary sticks much faster once you use it. A practical approach is to learn in layers. Start with the five characteristics and three service models, then move to deployment models, and only after that dig into compute, storage, and networking specifics.
Most major providers offer free tiers or trial credits, so you can launch a small virtual machine, upload a file to object storage, and see the billing dashboard for yourself. Set a budget alert first. Entry-level certifications from the major providers can also give your learning some structure, though hands-on practice usually teaches more than memorization does.
Conclusion
Cloud computing looks intimidating mostly because of its language, not its ideas. At its core, it is about renting shared, metered, on-demand resources instead of owning them. From that single idea come the service models (IaaS, PaaS, SaaS), the deployment choices (public, private, hybrid, multi-cloud), and the practical concerns of cost and security.
If you keep only a few things from this Droven.io Cloud Computing Guide, make them these: know who manages what in each service model, understand that availability zones and regions serve different purposes, watch for egress and idle-resource costs, and remember that security is a shared job. With those foundations, new terms become much easier to place, and provider documentation starts to read like plain instructions rather than code words.
Frequently Asked Questions
What is the Droven.io Cloud Computing Guide?
It is an educational guide that explains cloud computing concepts, terms, and models in plain language. This version focuses on the core vocabulary readers need before working with any cloud provider.
What are the three main types of cloud computing?
The three main service models are Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). They differ in how much the provider manages versus how much you manage.
What is the difference between public and private cloud?
A public cloud is owned by a provider and shared among many customers. A private cloud is dedicated to one organization, either on its own premises or hosted by a third party.
What does “pay-as-you-go” mean in cloud computing?
It means you are billed only for the resources you actually use, usually measured by time, storage volume, or data transferred, instead of paying a fixed amount upfront.
What is the difference between scalability and elasticity?
Scalability is the ability to handle more work by adding resources. Elasticity is the ability to add and remove those resources automatically as demand rises and falls.
Who is responsible for security in the cloud?
Both sides. Under the shared responsibility model, the provider secures the underlying infrastructure, while the customer secures their data, access controls, and configurations.
Is serverless computing really serverless?
No. Servers still run your code, but the provider manages them entirely, so you never provision or maintain them. You simply pay for the code that executes.
