Fireside Chat with Wells Fargo: Building a Data-Centric Business Ready for Any Future
summary
A major Wells Fargo outage exposes that hundreds of legacy relational databases require manual, error‑prone failovers, while an active-active nonrelational platform continues running; that drives a decision to adopt distributed SQL for ACID transactions, built‑in horizontal scaling, and simpler orchestration so failovers become a button press. The team pilots YugabyteDB, co-develops missing features, targets lifting roughly 2000 workloads without rewrites, and prioritizes multi‑tenant cloud integration, resiliency, and operational manageability.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:22Nathaniel’s background
- 2:27Inflection point for distributed SQL
- 8:03Manual failovers unsustainable
- 13:42Evaluating distributed SQL
- 17:57Adoption path and enterprise readiness
- 21:08PostgreSQL compatibility
- 23:32Building community excitement
- 24:55Future vision for distributed SQL
related talks
29mDelivering Always-On Financial Services with
12mPower a Better Future
22mBuilding a Modern Data Foundation: A Conversation with OCBC's Head of Data Architecture
26mFireside Chat: Going Cloud-Native: Supercharging the Journey to Digitalization
19mEvolve: A Database Journey from Ground to Cloud
58mTales of Data Architecture Evolution
35mA Customer’s Journey: Migrating from NoSQL to a Cloud Native Distributed SQL Database
26mFireside Chat: Financial Services Evolution