Business processes / 8 / 12
Audit log
Someone in the back office changed a customer's bank account, the next payout went to a stranger, and nobody can prove who did it. This lesson builds an audit trail that answers who did what, when, from where, and what it looked like before and after, and that survives crashes, a growing table and an insider with database access.
- 14 min
- Intermediate
- 12 steps
- Changes without an actor
- 14 /day
- API p95
- 45 ms
- Audit on fast disks
- 0 GB
- Unnoticed tampering
- 0
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Back-office API → Customer databaseRequest
UPDATE customers
SET bank_account = '***',1
updated_at = now(),2
updated_by = 'backoffice'3
WHERE id = 'c_1187';
Response
UPDATE 1
-- old account: overwritten, gone4
-- updated_by: one shared service login for 40 staff
bank_account— The new value. Bank details are sensitive, so the lesson hides them.updated_at— Only the last change. The one before is lost.updated_by— A shared service account. It proves that someone used the back office, not who.gone— The previous value is lost, so even the damage cannot be measured.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies