Cloud Native vs. Platform Native vs...

on YouTube ↗14m

" summary

Timeline: DevOps (2007–2009), Twelve‑Factor (2011), Docker (2013), Kubernetes (2014), CNCF (2015). Core claim: cloud native requires the four building blocks — DevOps, 12‑factor apps, containers and orchestration — so applications remain portable and vendor neutral. Using proprietary managed services creates platform native applications that force significant refactoring to escape, while true portability demands building cloud agnostic apps that treat the entire cloud as the abstraction, not a single provider.

AI-written summary · about

" chapters (8)

1. 0:00Cloud native origins
2. 1:51Cloud native building blocks
3. 4:02Cloud native hype bubble
4. 6:56Hype vs paradigm
5. 8:20Platform native architectures
6. 10:30Platform native limitations
7. 11:57Truly cloud native apps
8. 13:45Closing thoughts

" related talks

• 03mGoing (cloud) NativeKevin Steward · O'Reilly Software Architecture Conference New York 2018
• 51mWhat Is This Cloud Native Thing Anyway?Sam Newman · NDC Copenhagen 2019
• 56mHistory, Fundamentals and Future of Cloud NativeBenjamin Nothdurft · Voxxed Days Cluj-Napoca 2022
• 42mCloud Native ApplicationsKarsten Samaschke · ContainerDays Hamburg 2018
• 55mWhat Does Cloud-native Mean Anyway?Grace Jansen · Developers Summit 2021
• 05mCloud native or cloud agnostic? The questions you need to askSriram Rajan · Cloud Native Security Day Europe 2020
• 11mThe Makings of a Modern Application ArchitectureSam Ramji · O'Reilly Software Architecture Conference 2015
• 27mCloud Native: why, oh why?Emmanuel Bernard · Voxxed Days Microservices 2019