Building a Framework for Big Infra Decisions
summary
Practical rules for picking VMs, containers, or both: VMs win for lift‑and‑shift, non‑standard telecom protocols (SIP/GTP) and mixed OS stacks; containers win for new cloud‑native apps and higher density, though operators sometimes create giant non‑cloud‑native pods for 5G. Example customers start 100 VMs for 2–3 hours daily to batch work. Deployment options: public cloud (bill shock), on‑prem (higher CAPEX, hard to right‑size), Equinix Metal as metal‑cloud, hybrid/multi‑cloud tradeoffs, and partner builds that boot in a couple of days.
AI-written summary · about
chapters (4)
- 0:00Start
- 14:52Key Infrastructure components
- 15:55An ideal enterprise cloud
- 22:55What to expect from an Infrastructure Partner?
related talks
22mRight Abstraction
20mDeployment Strategies for Cloud Applications: Intel Case Study
01h 00mEvolving to Cloud Native
56mBusy Architect’s Guide to the Cloud Offerings
25mBuilding Applications in the Cloud
41mModernizing Legacy Apps - Platforms and Strategies
30mUsing the Theory of Constraints to Prioritize Applications for Migration to Cloud Foundry
33mRe-thinking the journey to the cloud