What Cloud Computing Actually Is

This is the first article in a plain-language, provider-neutral introduction to cloud computing. It is meant as a preliminary course, the groundwork that comes before the separate, deeper series on Microsoft Azure and AWS. The aim here is not to make you an expert. It is to make the language and the core ideas feel familiar, so that when you do pick a provider, the specifics have somewhere to sit.

So before we go anywhere near a particular platform, we need to answer a simple question. What actually is cloud computing?

The clouds as seen from my garden this June

Learning cloud computing can feel strangely abstract at first.

With ordinary software, you can often point to the thing you are building. A website. An app. A database. A form. A login page. Something visible.

Cloud computing is different. A lot of the important work happens in places you will never physically see, and that is what makes it feel slippery to begin with.

What is cloud computing?

At first, "the cloud" can sound like a vague marketing term, and indeed, some ways it is.

People use it to describe almost everything now. Files are in the cloud. Apps run in the cloud. Companies move to the cloud. Developers deploy to the cloud.

But underneath the phrase, the idea is fairly practical.

Cloud computing is the delivery of computing services over the internet.

Instead of owning and managing all the physical infrastructure yourself, you use services provided by a cloud platform. These services might include storage, computing power, networking, databases, analytics, artificial intelligence, security tools, and much more.

In a traditional environment, a company might need to buy physical servers, install them in a data centre, configure the network, manage the hardware, replace failed components, and plan capacity months in advance.

With cloud computing, many of those responsibilities shift to the cloud provider.

graph LR subgraph Traditional A[Your organisation] --> B[Buys servers] A --> C[Runs storage] A --> D[Manages networking] end subgraph Cloud E[Cloud provider] --> F[Runs the infrastructure] F --> G[Services over the internet] G --> H[Your organisation] end %% cc-caption: Traditional on-premises: you buy and run everything yourself. Cloud: the provider runs the infrastructure and you consume services over the internet.

That does not mean the cloud magically removes all technical work. You still need to design, configure, secure, monitor, and manage your systems properly. But the starting point changes. Instead of thinking, "What hardware do we need to buy?", you can think, "What service do we need to use?"

That shift is one of the main reasons cloud computing has become so important.

The main types of cloud services

Cloud platforms provide a huge range of services, but for a beginner it helps to group them into a few broad categories.

These are not the only services a cloud platform offers, but they are a useful starting point. Storage, compute, networking, and monitoring appear again and again in cloud systems, so it is worth getting comfortable with them early.

Infographic titled “Cloud Platforms: Core Service Categories” explaining four beginner-friendly groups of cloud services. The categories are Storage, for files, images, logs, databases, backups, and customer or product data; Compute, for running workloads using virtual machines, containers, web apps, or serverless functions; Networking, for connecting services securely, controlling traffic, and linking cloud systems with company networks; and Analytics and Monitoring, for tracking performance, logs, alerts, dashboards, security, and automated responses.

Where this series goes next

Cloud computing is not really one thing. It is a way of building and running systems that changes how you think about hardware, cost, and responsibility. Most cloud providers offer broadly the same building blocks, and the underlying ideas are shared across all of them. Microsoft Azure and AWS each have their own names, portals, and quirks, but those specifics are covered in their own later series rather than here.

For now, the goal is the foundation. Over the next articles we will look at how systems grow and shrink with demand, the scalability that makes that possible, and how the consumption-based pricing model changes the way you pay for what you use. We will work through the service models and deployment models, the language people use to describe who manages what and where things actually run. And we will spend time on the building blocks themselves: compute, storage, networking, and security.

None of it is as complicated as the marketing makes it sound. It is mostly a handful of practical ideas, explained one at a time, until you could explain them yourself.