hardDesignScenarioSeniorStaffLead
A regulator says this customer's data may not leave the country. How do you design for that?
7 min readUpdated 2026-08-15
Answer
Short answer
You pin every store to the region, including backups, DR, search indexes and key material, then hunt the paths that leave without anyone choosing to: telemetry labels, error traces, log shipping, support tooling and remote staff access.
Was this answer helpful?
Likely follow-ups
- Where does the identity provider live when users exist in three jurisdictions?
- How do you produce a group-wide revenue report without moving row-level data?
- What breaks about global uniqueness constraints, such as one account per email address?
- How would you prove residency to an auditor rather than assert it?
- When is a cross-border transfer permitted anyway, and what does that change in the design?
Related questions
- Your data is pinned per region, but login must be globally unique and admins want one global search. How do you build that?hardAlso on data-residency and multi-region6 min
- How do you design a petabyte-scale telemetry pipeline that decouples generation from storage while aggressively curbing backend SaaS costs?hardAlso on telemetry2 min
- A wrong answer from the model would cost real money. How do you put it in the product anyway?hardSame kind of round: design5 min
- Your observability bill is now bigger than your compute bill. What do you cut first, and what must you never lose?hardSame kind of round: scenario5 min