20 lines
1.6 KiB
Markdown
20 lines
1.6 KiB
Markdown
# Virtual Resource Deep-Dive
|
|
|
|
Virtual SCM focuses on the algorithmic flow of capacity rather than the physical flow of goods.
|
|
|
|
## Demand for Digital Content (The "Cat Meme" Effect)
|
|
When content goes viral, the virtual supply chain reacts through:
|
|
- **Immediate Elasticity:** The system senses a spike in CPU utilization $\rightarrow$ triggers auto-scaling $\rightarrow$ increases the "supply" of compute.
|
|
- **Edge Distribution:** CDNs replicate the asset (the meme) to edge servers, moving "inventory" closer to theuser to minimize latency.
|
|
- **Bottleneck Shift:** The constraint shifts from "production" (generating the page) to "network throughput" and "regional capacity limits."
|
|
|
|
## Cloud Capacity Procurement
|
|
- **Storage as a Commodity:** Services like **GCS (Google Cloud Storage)** and **S3 (Amazon S3)** treat vast pools of unstructured data as a scalable, virtualized commodity, abstracting the physical disks from the user.
|
|
- **Overcommitment:** Providers often "over-sell" virtual resources (e.g., CPU overcommitment), betting that not all tenants will peak simultaneously—a form of virtual inventory speculation.
|
|
|
|
## Mapping Virtual Services to Physical Resources
|
|
The "production" of a virtual service is the mapping of software requirements to physical hardware:
|
|
- **Generic Resources:** The primary raw materials are **CPU** and **RAM**.
|
|
- **Resource Stranding:** A critical failure in virtual SCM where a physical host has available CPU but is out of RAM, leading to wasted, unusable capacity.
|
|
- **Orchestration:** Tools like **Kubernetes** act as the "Supply Chain Manager," performing real-time planning and delivery of resources.
|