A shared notice board that lives entirely in the cloud. Nothing to install, no account to create — open it in any browser and you are already using software delivered as a service. Every note you post is stored centrally and instantly visible to everyone else viewing this page.
Software-as-a-Service means the application runs on the provider's cloud infrastructure and reaches you over the network — you consume it, you do not host it. The U.S. National Institute of Standards and Technology (NIST) defines five essential characteristics of cloud computing. Each card below states the characteristic and, in one sentence, exactly how this page demonstrates it.
A consumer can provision computing capability automatically, without human interaction with the provider.
Here: you started using the app the instant the page loaded — no signup, no email, no waiting for anyone to grant you access.
Capabilities are available over the network and reached through standard mechanisms from many kinds of client device.
Here: the same board opens on a phone, tablet, or laptop through any browser — the only requirement is an internet connection.
The provider's resources are pooled to serve multiple consumers, who share the same physical and logical infrastructure.
Here: every visitor reads and writes the one shared Workers KV store — you are all tenants of a single backing database.
Capabilities scale outward and inward automatically to match demand, appearing effectively unlimited to the consumer.
Here: the Cloudflare Worker spins up per request across a global network — one visitor or a thousand, nobody sized or booted a server.
Cloud systems automatically meter usage, so resource use can be monitored, controlled, and reported.
Here: Cloudflare counts every Worker invocation and KV read/write, and bills per request — you pay for exactly what is used, not for idle capacity.
Post a short note below. It travels to a Cloudflare Worker, gets stored in Workers KV, and reappears here — newest first — for every visitor. Refresh on another device to see the same shared wall.
Four cloud pieces, each doing one job. Data flows left to right on a write, and right to left on a read.
Cloudflare Pages hosts the frontend, the Worker is the stateless API layer that auto-scales per request, and Workers KV is the single multi-tenant store every visitor shares.
A cloud is simply a pool of computing resources you reach over a network instead of owning locally. Cloud computing is the practice of configuring and using that remote hardware and software on demand — storage, infrastructure, and full applications — without installing anything on your own machine. You rent capability over the internet and let someone else run the servers.
One shared pool of resources in the cloud, reached from any device over the network — exactly how you are using this page right now.
The deployment model describes who owns the infrastructure and who is allowed to use it. There are four.
Infrastructure is owned by a provider and shared over the open internet by many unrelated customers. It is the cheapest and most elastic option — this project runs on Cloudflare's public cloud.
Infrastructure is dedicated to a single organization, run on-premises or by a provider. It gives the most control and isolation, at higher cost, and is common where data must stay in-house.
Infrastructure is shared by several organizations with common concerns — the same industry, compliance rules, or mission — who pool resources while keeping outsiders out.
A mix of public and private (or community) clouds joined together, letting an organization keep sensitive workloads private while bursting less-sensitive ones onto cheaper public capacity.
The service model describes how much of the stack the provider manages for you. The more they manage, the less you have to operate yourself.
Purpose: rent raw compute, storage, and networking; you install and manage the OS and everything above.
Used for: hosting custom servers, disaster-recovery storage, large-scale batch compute.
Purpose: the provider runs the OS, runtime, and tooling so you only deploy code and data.
Used for: web-app backends, managed databases, CI/CD and deployment pipelines.
Purpose: the provider runs the whole application; you just use it in a browser.
Used for: email, CRM, collaborative documents, notice boards like the demo above.
This site implements the SaaS model. The Cloud Notes Wall in the live demo above is a finished application you use entirely in the browser — you never touch the server, runtime, or storage that Cloudflare operates underneath it.
Cloud computing did not appear overnight — it is the result of decades of moving compute away from the individual machine and toward shared, network-delivered resources.
The cloud is built on several older ideas that finally matured together. Four are essential.
Software slices one physical machine into many isolated virtual ones. This is what lets a provider pool hardware and hand each tenant an independent slice — the basis of resource pooling and elasticity.
SOA builds systems from small, loosely-coupled services that talk over standard network protocols. Cloud apps are assembled this way, so pieces can scale and be replaced independently.
Many networked computers act as one large pool to tackle big workloads together. This distributed-resource idea is what makes a cloud appear effectively unlimited.
Computing is metered and billed like electricity or water — you pay only for what you consume. It is the business model that makes on-demand, pay-per-use cloud possible.
Every cloud system has two halves connected over the internet: what the user sees, and the machinery that does the work.
In this project the front end is the page in your browser; the back end is the Cloudflare Worker and Workers KV store — connected, as always, over the internet.
NIST defines five essential characteristics that any true cloud service shares. They are the yardstick used throughout this subject.
Users provision computing capability automatically, whenever they need it, with no human on the provider's side involved.
Services are reached over the network through standard methods from phones, tablets, laptops, and desktops alike.
Providers pool their resources to serve many tenants at once, sharing the same physical and logical infrastructure.
Capacity scales out and back in automatically to match demand, appearing effectively unlimited to the user.
Usage is automatically metered, monitored, and reported, so consumers pay only for what they actually use.
The cloud trades ownership and control for convenience and scale. That trade brings clear advantages — and real risks worth weighing.