Hacker News Reader

I think an in-between approach could be:

1. Identify top-N tenants

2. Separate the DB for these tenants

The top-N could be based on mix of IOPS, importance (revenue wise), etc.

The data model should be designed in such a way that from rows pertaining to each tenant can be extracted.

This is how we did it at mailchimp. I think this is ignored or overlooked because this means devs might have to care a bit more about operations or the company has to care more.

That is what most tenanting scale-ups do. "Jumbo"-tenants get relocated either to separate partitions, or to partitions which are more sparsely populated.

Reply on news.ycombinator.com