Part 1 of 8 · 1 min read
Why this page comes ninth in Level 13
In this module you will
- Scope a wallet service and work out how many database nodes a target rate needs.
- Show why an in-memory store loses money on a crash and what an atomic transfer needs.
- Compare two-phase commit, try-confirm-cancel and a saga for a transfer.
- Explain event sourcing, commands, events, state and why it can be replayed for audits.
- Make an event log fast, safe and scalable with local files, snapshots, Raft and sharding.
The payment system (Level 12, page 4) moved money in from outside. A wallet moves money between accounts inside one platform, at a far higher rate, with an audit that must hold up. It joins transactions and consensus (Level 5), idempotency (Level 1), the queue (Level 12, page 1) and the ledger (Level 12, page 4). The book used is "System Design Interview, Volume 2" by Alex Xu, the digital wallet chapter. Numbers marked "made up" only show the idea.