Going (cloud) Native

on YouTube ↗03m

" summary

Argues that cloud‑native is team structure plus automation and architecture to manage complexity, not just tech; maps concrete specialization layers: IaaS/hardware ops (public cloud or bare metal), CoreOS, Project Atomic, RancherOS, VMware Photon for OS ops, then Kubernetes cluster ops providing self‑service developer tooling, and finally per‑application ops teams. Claims this split reduces cognitive load, lets app teams own operability, and produces more operable services in production.

AI-written summary · about

" related talks

• 43m(Mis)Understanding Cloud-NativeAna-Maria Mihalceanu, Rustam Mehmandarov · Voxxed Days Bucharest 2022
• 42mCloud Native ApplicationsKarsten Samaschke · ContainerDays Hamburg 2018
• 14mCloud Native vs. Platform Native vs...Ruckus Voxi · Cloud Native University Europe 2026
• 51mWhat Is This Cloud Native Thing Anyway?Sam Newman · NDC Copenhagen 2019
• 34mGoing cloud-native: Why? How? & What?Driss ALLAKI · BlaBlaConf 2022
• 27mCloud Native: why, oh why?Emmanuel Bernard · Voxxed Days Microservices 2019
• 02mHow to Choose Which Cloud Native Technologies...John Morello · Cloud Native Security Day 2019
• 31mCloud native: the cattle the pets and the germsAvishai Ish Shalom · DevOpsDays Tel Aviv 2018