Fireside Chat: Going Cloud-Native: Supercharging the Journey to Digitalization
summary
Claims a bank achieves 5S outcomes—self‑healing zero‑downtime, fully automated deploys, elastic scaling, measurable cost savings and airtight security—by adopting a cloud foundry PaaS and disciplined engineering practices like pair programming and extreme programming. Teams build a data‑and‑AI platform as a service, swap out 30–40% of modular components over five years, sustain velocity despite high developer turnover, and move toward cloud‑native distributed SQL (Yugabyte) to get Postgres/Cassandra compatibility plus transactional resilience.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:28Early cloud-native journey
- 3:15Key drivers for transformation
- 5:02Outcomes and lessons
- 7:30Scaling and sponsorship
- 8:35Cloud-native databases
- 10:00Data platform design
- 12:47Transactional databases
- 14:10Financial industry shifts
- 16:39Tech as competitive enabler
- 17:42MetLife’s tech priorities
- 18:22Engineering culture
- 20:28Diversity in tech leadership
- 21:52Safe innovation environments
- 23:38Women in tech leadership
- 25:05Closing remarks
related talks
26mFireside Chat: Financial Services Evolution
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
54mCloud Native Culture
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise
59mCloud Native Culture
23mHow to Build and Deploy Services in the Cloud fireside chat
26mCase Study of Success
40mGet Projects Approved By Articulating the Business Value Of a Cloud Native Solution