Cloud Deployment Models
Models that describe where cloud infrastructure runs.
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.
Use it when
- You are comparing where a workload should run for cost, control or compliance reasons.
- You need the standard definition of hybrid versus multi-cloud.
Watch out for
- Hybrid means mixing private and public infrastructure; multi-cloud means using more than one public provider. The two are often combined.
- Sovereign and distributed cloud are recent categories and are used inconsistently by vendors.
The data
9 rows
| Model | Description |
|---|---|
| Public | Services owned by a third-party provider and shared among customers. |
| Private | Infrastructure dedicated to a single organization. |
| Hybrid | Combines public and private clouds with orchestration. |
| Community | Shared infrastructure for a specific community with common concerns. |
| Multi-Cloud | Uses services from multiple cloud providers. |
| Distributed Cloud | Public-cloud services run from the provider's infrastructure placed in different physical locations, including a customer's, while still managed by the provider. |
| Edge Cloud | Compute placed close to users or devices to cut latency and bandwidth to a central region. |
| Sovereign Cloud | Cloud operated under the legal control of a particular jurisdiction to meet data-residency and sovereignty requirements. |
| Virtual Private Cloud | A logically isolated network within a public cloud where a customer defines address ranges, subnets and routing. |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| data | model | string | Public |
| data | description | string | Services owned by a third-party provider and sh… |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/cloud-deployment-models?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/cloud-deployment-models.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →