00 /What You Will Learn
By the end you will be able to
- Design production-ready payment architectures with zero double-charge risk and absolute financial balance.
- Reproduce the negative control: customer double-debit bugs caused by client retries during dropped network connections.
- Implement edge idempotency using Redis keys and unique transaction identifiers to deduplicate retried payments.
- Structure double-entry accounting journals where every transaction creates matching debits and credits.
- Enforce the transactional outbox pattern to publish domain events reliably without distributed two-phase commits.
- Execute distributed saga compensating transactions to reverse ledger entries when downstream bank gateways time out.
- Run automated midnight reconciliation audits to verify 100% balance parity across payment receipts and ledger entries.
Before you start
Finish Lab 33 (Transactional Outbox), Lab 34 (API Idempotency Key), and Lab 40 (Saga Pattern with Compensating Transactions) first. You should understand SQL transactions, cache TTLs, message queues, and compensating rollbacks. Docker Desktop must be running.