TLDR Tech / Data
Building High Throughput Payment Account Processing
To handle extreme "hot-key" traffic on high-activity payment accounts which previously hit sequential processing limits of 3–4 ops/sec per account, causing multi-hour processing times for bulk jobs, Uber uses a three-service architecture to batch financial updates into ~250 ms windows (using Redis for coordination/queuing) with an atomic write per batch, and offloads immutable audit logs asynchronously.
Read the full story