One Thing, Then Stop

1. Clarify the user and goal.
2. Name the core entities.
3. Define simple APIs.
4. Sketch the high-level flow.
5. Add DB/cache/queue only when needed.
6. Say one tradeoff.
7. Say one failure mode.

If today feels heavy, read only the title and write: “I touched it.” That counts.

Kafka, CAP, sharding, distributed consistency, and queue internals stay explain-only unless this is on.