Cloud Native Transformation Patterns
summary
Fictional mid‑size bank (200–300 people) tries two transformations: first slices cloud native into a backlog and after 6–12 months shows almost no delivery, second dedicates half the org and after 1–2 years only ~30% of the platform is done. Successful pattern prescribes a transformation champion, executive buy‑in, a small core team that runs experiments/POCs to an MVP platform (microservices, Kubernetes and Docker, CI/CD), gradual team‑by‑team onboarding, strangling the monolith, and a three‑horizon investment model; a downloadable deck of cards codifies the pattern language.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:58Who is the stranger
- 5:38Delivery of value faster
- 11:48What is Cloud Native
- 15:25Creativity vs Proficiency
- 20:13Patterns
- 22:15What happened
- 22:42How to design successful transformations
related talks
01h 00mEvolving to Cloud Native
26mFireside Chat: Going Cloud-Native: Supercharging the Journey to Digitalization
39mThe Power of Cloud Native in Financial Institutions
23mThe Nine Journey: Cloud Native Transformation
42mCloud Native Applications
59mCloud Native Culture
44mNine Ways To Fail at Cloud Native
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise
