The great cloud repatriation is real, but smaller than the headlines
Some workloads are moving back to owned hardware. Most are staying put. The difference is predictability.
13 stories
Some workloads are moving back to owned hardware. Most are staying put. The difference is predictability.
The container orchestrator is now boring infrastructure. The interesting work is happening in the layers above it.
Functions found their niche: glue, events and bursty jobs. Everything else went back to containers.
Regulatory pressure and challenger clouds have forced the big providers to cut the price of leaving.
A configuration push, a cascading failure and a recovery slowed by the very tools meant to speed it.
Analytics engines are reading directly from cheap blob storage, and the warehouse is becoming a query layer.
Forget autonomous cars. The workloads that moved to the edge are video analytics, retail and factory sensors.
Logs, metrics and traces have grown faster than the systems they describe. Teams are starting to push back.
Operated locally, legally separated from its American parent, and priced to compete. Whether it satisfies regulators is the open question.
New tools validate cloud configurations before deployment, catching the misconfigurations behind most breaches.
No spam. One email a week. Unsubscribe anytime.
One email a week: the breaches that matter, the patches to apply, and the tools we actually tested. No filler, unsubscribe anytime.