4 ms·
If you don't have to share data between users, a multi-database setup is the way to go. I wrote a post about how I do it a little over a year ago... https://to
by tomschlick 10y ago
If you don't have to share data between users, a multi-database setup is the way to go. I wrote a post about how I do it a little over a year ago...
https://tomschlick.com/2015/11/29/lessons-from-building-multi-tenant-apps-part-1-databases https://tomschlick.com/2015/11/29/lessons-from-building-mult...
- raarts 10y agoWhat is your experience with doing schema upgrades across many databases? Is it usually possible to break up schema changes in small pieces, so that it works across multiple versions of your software?
- tomschlick 10y agoYeah we try to minimize the changes that would require a lock. For those cases we have a flag where we can turn off each tenant individually for maintenance. For long running / many record migration we shove those into a queue to they can be done in the background in parallel.
- icebraining 10y agoThanks for that! We run an isolated model (one database + app process per client), but sometimes it seems like there isn't any good help out there, with everyone building completely shared apps.