4 ms·
> One database per account/user data store This is very interesting to me. I am writing a multi-tenant app with a single RDBMS schema right now and balancing a
by hungerstrike 9y ago
> One database per account/user data store
This is very interesting to me. I am writing a multi-tenant app with a single RDBMS schema right now and balancing all of my needs (scaling/sharding, partitioning tables, normalizing vs denormalizing) has been challenging.
I've never written a system with a whole database per account. Does anyone have any good reading or examples on this general tactic?
- Clubber 9y agoIt has it's plusses and minuses. The plusses are that everything is isolated and the data doesn't get too big. It becomes problematic when you need to access multiple clients at the same time (and you probably will at some point). Deployment is harder since you have to do it more. Keeping schema versioning straight is also a pain. Data isolation is inherent in single tenant though.
- ddorian43 9y agoSee actordb