Building a Bank (with DDD, Microservices, and Autonomous Teams)
summary
Upvest builds a greenfield banking stack: external REST external / Kafka internal APIs, microservices in Golang + Kafka, and a minimal cloud platform with infrastructure-as-code and CI that records 4 ICE approvals per deployment. The system supports continuous delivery and regulator audits, scales to about 80 engineers in three tribes, but faces tech-sprawl, uneven domain complexity (taxes, corporate actions) and coordination pain. Responses include an architecture guild, staff-engineer enabling work, lightweight value-stream reorgs, and more investment in platform engineering to restore alignment.
AI-written summary · about
chapters (7)
- 0:00Introduction and company background
- 3:47Starting from scratch with strong principles
- 12:11Growth challenges and organizational changes
- 20:11Architecture management evolution
- 31:23Current structure and future outlook
- 36:59Team processes and domain-driven design learnings
- 40:29Q&A and closing remarks
related talks
55mBuilding a Bank with Go
37mStone Bank: how a team of initially 5 (...)
46mA Microservices Experience in Banking
51mMicroservices in Go
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
30mBuilding a Scalable, Compliant, Multi-Cloud Bank with a Service Mesh
35mBuilding a Bank with Kubernetes
44mRoute to microservices the epic voyage of a fintech leader