Database Sharding Strategies
The cluster focuses on debates around database sharding for multi-tenant SaaS applications, comparing single large databases, per-tenant schemas or instances, and hybrid approaches for scaling and isolation.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Give each business or customer its own schema and you almost never need sharding.
You mean it's easier to shard databases per tenant when it's a monolith?
Why a single postgres? Why not shard by users?
Using a sharded database is not just for scale.
99% of apps never need to shard data. Probably closer to 99.9% if they are single tenant.
Not if you're sharding correctly.
Isn't that what sharded databases do?
You shard for load distribution. If data isolation is #1 priority, use separate tables, schemas, database instances.
Very likely a monolith database (the sharding gives it away) that uses a multi-tenant architecture (`WHERE account_id = ?`)
It's not really an issue if you have 1 db per customer