Tenant data layout
Difficulty 3 of 5
Your app serves 100 small tenants: 2,000 requests/s in total, steady load. One Postgres server with 200 connections fits all of it. You have 80 USD/mo. Pick how to keep the data of each tenant apart. Keep errors under 0.1 percent.
Options
- Shared tables, tenant ID
- A schema for each tenant
- A database for each tenant
Goals and limits
- Error rate
- under 0.1%
- p99 latency
- under 150 ms
- Monthly cost
- under 80 USD/mo
- Traffic
- 2,000 req/s
Concepts
How players did
Player results load from the server.