Re:Shardines: SQLite3 Database-per-Tenant with ActiveRecord
by leetrout on Sunday April 27, 2025 @02:30PM
(#43814059)
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.
Re:Shardines: SQLite3 Database-per-Tenant with ActiveRecord
by julik on Sunday April 27, 2025 @02:44PM
(#43814165)
That is what most tenanting scale-ups do. "Jumbo"-tenants get relocated either to separate partitions, or to partitions which are more sparsely populated.
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.