3 ms·
I worked for a company that did this, we had hundreds of database instances, one per customer (which was then used by each of those customers' employees). It w
by swlkr 6y ago
I worked for a company that did this, we had hundreds of database instances, one per customer (which was then used by each of those customers' employees).
It worked out pretty well. The only downside was that analytics/cross customer stats were kind of a pain.
The customers all seemed to like that their data was separate from everyone else's. This never happened, but if one database was compromised, everyone else's would have been fine.
If I were starting a B2B SaaS today where no customers shared data (each customer = a whole other company) I would use this approach.
- Polylactic_acid 6y agoIt has been an actual requirement from our customers that they don't share an instance or database with other customers. It also seriously limits the scope of bugs in permissions checks. Sometimes I will find a bit of code that should be doing a permissions check but isnt which would be a much bigger problem if it was shared with other companies.