Building a distributed payment system to handle scale
summary
Describes GO-JEK’s design choices and architecture for a payments backend that copes with rapid growth and traffic spikes, covering resilience, fault tolerance, distribution and eventual consistency. Mentions handling both cash and digital transactions and the technologies/architectural approaches used to scale the system for large, increasing transaction volumes.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:04Before we begin
- 1:44What are we?
- 3:19Payments
- 5:02Considerations
- 6:05Up front decisions
- 8:47WELL, WHAT CAN GO WRONG
- 9:15Early days
- 12:033rd January
- 14:15Double the fun
- 16:11Tale of two DCs
- 19:01Other lessons
- 20:18Team structure
related talks
49mPayment System: Survival Guide
24mBuilding Planet-Scale Payment Platforms
55mBuilding a Bank with Go
48mPayments: The Next Frontier
45mE-commerce platform. Core build principles, problems and guidelines.
37mThe Need For Speed: Scaling Go Microservices - Artur Kondas
43mWhy Use GO in Financial Services
13mLow-Maintenance Backend Architectures for Scalable Applications