Building a Bank with Go
summary
A new bank stack is implemented almost entirely in Go: hundreds of small microservices in Go compile to static binaries, deploy in Docker on Mesos/Marathon, and communicate over an AMQP transport with protobuf (proto3) messages. Core pieces include in-house libraries mercury and titan, a tracing/metrics tool phosphor, and async enrichment pipelines (Google Places, Foursquare) that attach merchant metadata. Card flow uses fast authorizations, background reconciliation and compensating cleanup rather than distributed two‑phase commits; testing includes unit, acceptance and chaos-style fault injection. Launching debit cards and mobile alpha is underway.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 4:05Example app
- 5:10Debit cards
- 5:55Monty Python
- 7:37Single responsibility
- 9:20Load balancer
- 10:00Microservice architectures
- 10:55Libraries
- 11:43HTTP
- 12:52Services
- 13:48Code
- 18:33API
- 22:49Aggregation
- 27:58Deployment
- 30:34Complexity
- 31:55Testing
- 34:30Monitoring
- 35:59Distributed Tracing
- 40:52Questions
- 43:24Distributed Transactions
- 45:33Integration Testing
- 46:41Security
- 49:42Latency
- 52:06Security auditing
related talks
51mMicroservices in Go
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
01h 03mGo & Microservices
01h 02mBuilding Microservice Architectures with Go
43mWhy Use GO in Financial Services
35mBuilding a Bank with Kubernetes
31mBuilding a microservices architecture with Go
28mHow to Structure Your Microservices