Internet as a Platform

The Internet is not merely a communication network — it is the foundational delivery platform for all cloud computing services. Understanding how the web evolved from a document-sharing system into a programmable, service-oriented infrastructure explains why cloud computing became possible.

From Web 1.0 to Cloud

• Web 1.0 (1990s): Static HTML pages, one-way communication, server-rendered content
• Web 2.0 (2004–2010): Dynamic, user-generated content, AJAX, REST APIs, social platforms
• Cloud Era (2006–present): Infrastructure, platforms, and software delivered as services over HTTP

Amazon's launch of AWS EC2 and S3 in 2006 marked the inflection point where the Internet became a commercial utility platform for computing resources.

Key Enabling Technologies

• HTTP/HTTPS: The universal application-layer protocol enabling stateless request/response cycles across any device
• REST (Representational State Transfer): Architectural style using standard HTTP verbs (GET, POST, PUT, DELETE) to expose resources as URLs — the backbone of every cloud API
• JSON/XML: Lightweight data-interchange formats enabling interoperability between heterogeneous systems
• DNS: Global naming system that routes billions of daily requests to geographically distributed datacenters
• CDN (Content Delivery Network): Edge caching (CloudFront, Akamai) reduces latency by serving content from nodes close to end users
• OAuth 2.0 / OpenID Connect: Federated identity standards that allow single sign-on across cloud services

The Browser as Universal Client

The web browser has become the universal thin client for cloud applications. Instead of installing software locally, users access SaaS applications (Gmail, Salesforce, Office 365) through a browser. This shift:

• Eliminates client-side software deployment and update costs
• Enables cross-platform access (Windows, macOS, Linux, mobile)
• Centralizes data in the cloud rather than on endpoint devices
• Supports real-time collaboration (Google Docs, Figma)

Standards Enable Interoperability

Open standards prevent vendor lock-in and allow composable cloud architectures:

• OpenAPI / Swagger: Describe REST APIs in a machine-readable format
• OCI (Open Container Initiative): Standardize container image and runtime formats (Docker, containerd)
• Kubernetes API: Standard interface for container orchestration across AWS EKS, Azure AKS, GCP GKE

Architecture: Internet-Enabled Cloud Request Flow

Why This Matters for Cloud Architecture

Because cloud APIs are accessed over the Internet using standard protocols, organizations can:

• Compose services from multiple cloud providers (multi-cloud)
• Automate provisioning with Infrastructure as Code tools (Terraform, AWS CDK) that call cloud APIs
• Integrate third-party SaaS into applications via webhooks and REST APIs
• Build globally distributed systems that serve users on any device, anywhere

The Internet as a platform means cloud resources are only an API call away.