Cloud outages are a dependency problem, not a Microsoft problem
DavidLinthicum · x · 2026-11-17
Cloud architect David Linthicum argues the recent Microsoft 365 outage exposed a dependency problem, not a vendor problem.
- When email, calendars, and collaboration tools fail together, blaming the provider and migrating in panic isn't a strategy.
- The same risk applies to AWS, Google Cloud, Salesforce, ServiceNow, Oracle, and every platform embedded in enterprise operations.
- The core issue is visibility: most organizations don't understand their system dependencies until something breaks.
His takeaway: enterprises need dependency visibility and governance, not a provider swap.
More from Infra
- Microcenter posts deepest GPU discounts in months: RTX PRO 6000 drops $4,000, still above MSRP — OvertaxedOne · 2026-11-17
- Intel shares first Crescent Island D270 benchmarks: 29% lower AI latency than RTX PRO 6000 Blackwell — pulse77 · 2026-11-17
- Is remote desktop GPU access a practical alternative to high-end laptops? — robertwellesley · 2026-11-17
- gputaskman: an open-source htop for your GPU that breaks down VRAM by process and LLM KV-cache — alex_verem · 2026-11-17
- Megaspeed Got $800M in Nvidia Chips After No-Sell Listing, Faces Criminal Probe — GaryMarcus · 2026-11-17
- llama.cpp PR rotates K/V read order to boost L2 cache hits, big long-context speedup — jacek2023 · 2026-11-17