AdvancedSystem-Design
45 min
Design a Multi-Tenant SaaS Platform
Multi-TenancySecurityBillingSRE
Advertisement
Interview Question
Design a SaaS platform with tenant isolation, noisy-neighbor controls, per-tenant config, and usage-based billing.
Key Points to Cover
- Isolation models: shared DB with tenant keys vs siloed DBs
- Per-tenant quotas, rate limits, and resource pools
- Config/feature flags by tenant; migrations and seeding
- Metering, usage pipeline, and billing reconciliation
- Observability and SLOs per tenant; noisy-neighbor detection
Evaluation Rubric
Clear tenant isolation strategy30% weight
Quota/rate limit and fairness plan25% weight
Accurate metering & billing design25% weight
Tenant-level SLOs & observability20% weight
Hints
- 💡Consider tenant routing keys for sharding.
Potential Follow-up Questions
- ❓How to migrate a tenant between shards?
- ❓How to handle per-tenant encryption keys?
Advertisement