From the engine to the bridge - building systems that scale
summary
Builds a payments platform with a partitioned front-end and back-end SQL setup, a rules engine that packages XML payloads into a job queue, and 250 worker agents (initially idle desktops, later virtualized) to replay state and guarantee two-sided accounting. Handles split settlement via virtual accounts, sends bursts of 150–200 TPS while throttling gateways, processes billions in transactions over years, raises $50M, takes three years to onboard the first 100 banks and targets 500 banks by year end. Keeps a $10M cash buffer to pass vendor risk checks.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 4:27From developer to CEO
- 12:11Early technical challenges
- 22:40Architectural solutions and scaling
- 30:23Technology vs business value
- 33:09Transition to fintech leadership
- 37:27Fintech industry inflection point
- 40:18Banking partnerships and distribution
- 45:13Customer understanding and growth
- 45:55Closing remarks and Q&A
related talks
17mExtreme Engineering-Elements of Building a High -scale Broking Application
37mStone Bank: how a team of initially 5 (...)
58mDEVOPS in a Multi-Banking World
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
22mBuilding Building Blocks
34mCrafting the Core - Why and How We Built the Core Banking System
29mNavigating regulated scale: How Fiserv hones golden paths for 7,500 developers
36mHigh Availability at Braintree