2019 10 30 ST Linkit ST 1145 1215
summary
A traditional finance firm tries Kubernetes, splits half a team, and stalls for 6–12 months with no production result; cloud native requires roughly 20 different tools and proper CI/CD or microservices explode delivery cost. A small core team builds a minimal platform and gets to production in 3–6 months MVP platform, with gradual onboarding so the platform team of 5–10 platform support isn’t overwhelmed. Success depends on staged investment, experiments and shifting culture from creative to algorithmic practices.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:11Meet the fictional company WasGreat
- 2:16Strangers in financial industry
- 4:47Why cloud native matters now
- 7:14Failed first attempts at cloud native
- 8:19What cloud native really means
- 10:50The real problem with legacy systems
- 11:56Creativity vs proficiency in transformation
- 14:13Patterns for cognitive transformation
- 16:28Why previous attempts failed
- 17:53How to design a successful transformation
- 20:20Culture as the key to change
- 21:28Balancing innovation and delivery
- 22:10Cloud native is about mindset
- 22:51Strangers are already here
related talks
40mLessons Learned Building Developer Platforms
21mFrom Zero to Prod in 2 Months with a Team of One
15mPlatform Engineering - About Tools...
31mThe 20 Year Platform – bringing together Kubernetes, 12-Factor and Functions
23mA Practical Guide To Cloud Native Solutions: Demonstrating ROI and Business Impact
29mBuilding a Start-Up to Compete with Ourselves
39mStrangling the Legacy with Kubernetes
29mUnlocking Developer Efficiency