Blog / Tech, New & Old /

The rise of cloud computing: AWS and friends

Before the cloud, if you wanted to run a website or an app, you bought a server. A physical machine. You put it in a room, gave it power and cooling, and hoped nothing broke on a Friday night.

Today you can rent the same power for a few minutes, switch it off and pay only for what you used. That shift is called cloud computing, and a company best known for selling books helped start it.

Then: the server in the cupboard

For a small company in the 1990s or early 2000s, running software meant:

  • Buying hardware upfront, often for the busiest day you could imagine.
  • Housing it somewhere, either in your own office or in a rented rack at a data centre.
  • Looking after it: updates, backups, replacing failed disks.
  • Waiting weeks to add capacity, because ordering and installing machines took time.

If your site suddenly got popular, you could be overwhelmed. If it didn’t, your expensive machine sat idle. Either way, you’d paid in advance.

Web hosting companies softened this. You could rent a slice of someone else’s server. But you were still limited to what the plan offered.

What the cloud changed

The core idea: instead of owning computers, you rent computing as a service, on demand and by usage. Like electricity. You don’t build a power station to run your lights; you plug in and get a bill.

In 2006, Amazon Web Services launched two services that set the pattern. S3 stored files, and EC2 let you rent virtual servers by the hour. A developer with a credit card could get a server in minutes, with no purchase order and no cupboard.

Others followed. Microsoft launched Azure in 2010. Google had begun with App Engine in 2008 and built out Google Cloud over the years. Many smaller providers joined in. I explained the three big names in cloud hosting: AWS, Google Cloud and Azure for normal people, and what the word means in what the cloud really means.

Why it took off

  1. No big upfront cost. A start-up could begin small and grow.
  2. Speed. Setting up a new server took minutes, not weeks.
  3. Scaling. Capacity could rise on a busy day and fall afterwards.
  4. Reliability. Big providers spread systems across multiple data centres.
  5. Services built on top. Databases, email, storage, machine learning and more became things you rented instead of built.

Much of what you use daily runs on this: streaming services, banking apps, online stores, many AI tools. Even if you never log in to a cloud console, your apps probably do.

The three layers, in simple terms

The industry uses some jargon. Here it is as a restaurant.

Term What it means Restaurant analogy
IaaS (infrastructure) You rent raw servers and storage You rent an empty kitchen and cook yourself
PaaS (platform) You rent a ready environment to run your code You rent a kitchen with the equipment set up
SaaS (software) You use finished software online You eat at the restaurant

Most people use SaaS without thinking about it: email, online docs, a Shopify store.

What it did well

  • It lowered the barrier to starting things. Many online businesses and tools exist because renting was cheap.
  • It made global reach easier, with data centres in many regions.
  • It turned maintenance into someone else’s job.

What it costs, and the catches

  • Bills can surprise you. Pay-as-you-go means a mistake or a traffic spike can run up charges.
  • Lock-in. Once you build around a provider’s special services, moving is hard.
  • Outages happen. When a big provider has a problem, a large part of the internet notices. I wrote about the effect of one faulty update in the CrowdStrike outage, which was a different kind of failure, but a reminder of how connected everything is.
  • Complexity. Cloud consoles can be overwhelming for beginners.
  • Distance. If the data centre is far from your users, pages can be slower. For African sites, that matters.

What this means for a normal website

You don’t have to use AWS directly to benefit from the cloud. Many hosts, website builders and shops run on cloud infrastructure behind the scenes. For a small site, a good managed host or a platform like Shopify is usually simpler than building on raw cloud services.

Raw cloud makes sense when you need control, specific technology or large-scale traffic, and when someone on the team knows how to manage it. For everyone else, the question isn’t “which cloud?” but “who looks after this, and what happens if it breaks?”

Common myths

  • “The cloud is somewhere vague.” It’s real computers in real buildings, owned by someone.
  • “The cloud is always cheaper.” Often at small scale; not always at large scale or with careless setups.
  • “The cloud is automatically secure.” Providers secure their part. You must secure your settings and accounts.
  • “Cloud means no backups needed.” You still need backups.

A scene from a small business

Say you run a small online shop and a celebrity mentions you on a Saturday. In the old world, your single server melts, and you spend the weekend apologising. In the cloud world, extra capacity can be switched on within minutes, and switched off on Monday. That ability to stretch and shrink is the heart of the idea, and it’s why even modest businesses now build on top of it, often without noticing.

Key takeaways

  • Cloud computing means renting computing power and services on demand.
  • AWS launched S3 and EC2 in 2006; Azure and Google Cloud followed.
  • It cut upfront costs and sped up everything, but added cost surprises and lock-in.
  • Small sites rarely need raw cloud services; managed hosting is often enough.

Do you know where your own website actually lives? If not, that’s a good first question to answer this week.