3 ms·
Even then, it would be better phrased as a tradeoff. What's the downside of putting in the database? I'd guess it makes horizontally scaling harder, and it's le
by blowski 5y ago
Even then, it would be better phrased as a tradeoff. What's the downside of putting in the database? I'd guess it makes horizontally scaling harder, and it's less portable to other database vendors. Is there an upside, like you've got stronger data security guarantees?
- picardo 5y agoGood point. Phrasing it as a trade-off is the better approach. Agree with the downsides you listed, as well. Better security guarantees, for sure, but if an unauthorized user gains direct access to your database, you might have bigger problems from a security perspective.
- pfarrell 5y agoAgree with all points here. An upside to using db to handle data permissions is the data has the same protections if you are accessing with direct SQL or using an app. Also, those permissions would persist with the data in restored backups. I’m not advocating this and think for OLTP, building RBAC in the app layer is almost always a better idea, but these would be some benefits.