api: YAML JSON TOON Database
version: 1.0.0
format: toon
category:
  id: 399
  slug: cloud-computing
  name: Cloud Computing
  description: "Cloud service models, providers, and deployment patterns."
  icon: cloud
  created_at: 1783090350
  dataset_count: 7
  topic:
    overview: "Cloud-computing reference data covers how computing is rented and run: who manages which layer (IaaS, PaaS, SaaS and their descendants), where it runs (public, private, hybrid and multi-cloud), how workloads are packaged (containers and the tools that orchestrate them) and the serverless model that bills by execution. The service-model names are marketing-adjacent categories rather than strict standards, and vendors blur them, so the useful question is always 'which layer do I manage, and which does the provider manage'."
    key_ideas[7]{term,meaning}:
      Shared responsibility,The provider secures and operates the layers it manages; the customer secures what it deploys on top. Moving from IaaS to SaaS shifts more responsibility to the provider.
      Elasticity,"Capacity that grows and shrinks with demand and is paid for as used, rather than provisioned for the peak."
      Container,"A packaged process with its filesystem and dependencies, isolated by the host kernel. It is lighter than a virtual machine because it shares the kernel."
      Orchestration,"Automating placement, scaling, networking and recovery of many containers; Kubernetes is the dominant system."
      Serverless,"A model where the provider runs and scales code on demand and bills for execution, so servers still exist but are not managed by the customer."
      Region and availability zone,Regions are geographic areas; zones are isolated data centers within a region. Spreading across zones protects against a single data-center failure.
      Vendor lock-in,Dependence on provider-specific services that makes moving workloads costly.
    pitfalls[4]: "Assuming 'the cloud' removes operational work. Someone still owns security configuration, cost control, backups and reliability design.",Treating multi-cloud as free resilience. It adds cost and complexity and does not help unless the application is built to use it.,Equating containers with isolation as strong as virtual machines. A shared kernel is a larger attack surface.,Ignoring cold starts and per-invocation limits when choosing serverless for latency-sensitive paths.
    agent_tips[3]: "When asked about a service model, state which layers the customer manages in each, not only the acronym.","Give provider examples as examples, not recommendations, and note that product names change.","For pricing questions, say that rates and free tiers change and point to the provider's current pricing page."
    start_with[2]: cloud-service-models,container-orchestration
datasets[7]{id,slug,title,description,tags,view_count,created_at,entry_count,summary}:
  2745,cloud-deployment-models,Cloud Deployment Models,Models that describe where cloud infrastructure runs.,"cloud,deployment,hybrid",37,1793403093,9,"The ways cloud infrastructure is deployed: public, private, hybrid, community and multi-cloud, plus distributed, edge and sovereign variants and the virtual private cloud network boundary. Each row says who owns and uses the infrastructure."
  2746,cloud-service-models,Cloud Service Models,Service models that define the level of management shared.,"cloud,iaas,paas,saas",41,1793403093,9,"The service models of cloud computing, from infrastructure (IaaS) through platform (PaaS) and software (SaaS) to function, container and desktop services, plus backend, database and machine-learning services. Each row gives the model, what the provider manages and example products."
  2758,container-orchestration,Container Orchestration,Tools and concepts for managing containers at scale.,"cloud,containers,kubernetes,docker",54,1793403093,19,"The terms of container orchestration, led by Docker and Kubernetes: containers, pods, services, deployments and Helm, plus the Kubernetes objects and components that keep workloads running such as nodes, namespaces, ingress, config, storage and autoscaling."
  2759,containerization,Containerization Concepts,Key concepts and terminology in containerization and container orchestration.,"cloud,containers,docker,kubernetes,devops",38,1793403093,14,"The concepts behind containers: images, runtimes, registries, orchestration and service meshes, with the Linux kernel features and open standards underneath them, namely namespaces, cgroups, layered file systems and the OCI specifications, and the tool commonly associated with each."
  2841,major-cloud-providers,Major Cloud Providers,Leading public cloud computing platforms.,"cloud,providers,aws,azure,gcp",48,1793403093,11,"The largest public cloud providers with their type and flagship services: AWS, Microsoft Azure, Google Cloud, IBM Cloud, Oracle Cloud and Alibaba Cloud, plus developer-focused and regional providers such as DigitalOcean, Cloudflare and Hetzner."
  2890,serverless-patterns,Serverless Architecture Patterns,Common patterns for designing serverless applications.,"cloud,serverless,lambda,functions,architecture",25,1793403093,10,"Architecture patterns used with serverless platforms: event-driven flows, API gateway plus functions, CQRS, backend-for-frontend, workflow orchestration and static content with functions. Extra rows add fan-out, queue-based load leveling, scheduled jobs and webhook handlers."
  2889,serverless-computing,Serverless Computing,Concepts and terms for serverless architectures.,"cloud,serverless,functions",38,1793403093,13,"The core ideas of serverless computing: functions as a service, event-driven execution, cold starts, statelessness, API gateways and pay-per-use billing, plus the operational concepts that matter in practice: concurrency, timeouts, idempotency, scale to zero and lock-in."