This question evaluates a candidate's ability to design a scalable, low-latency in-game currency subsystem covering transfer semantics, double-spend prevention, data modeling, APIs, and near real-time plus historical analytics.
You are designing the in‑game currency subsystem for an online game. Players can transfer currency between accounts. Product and ops need:
Assume a single in‑game currency, high read volume, and strict prevention of double‑spending. All timestamps are UTC.
Deliver data models, APIs, and any supporting components necessary to meet these requirements with low latency and correctness.
Login required