4 ms·
> But then again: Is it even a good idea to access the same database from two codebases at all? A motivation for relational algebra was different applications
by hyperpallium 7y ago
> But then again: Is it even a good idea to access the same database from two codebases at all?
A motivation for relational algebra was different applications accessing data in different ways. This integration remains a selling point. Further, data often outlasts applications... even languages.
- _visgean 7y agothe problem is that these days you need a lot of application code to check for permissions and that kind of stuff.
- dllthomas 7y agoIn principle permissions can go in the DB.
- bayesian_horse 7y agoIn practice this is rarely ever done (right). Row-level permissions are possible, but it can get more complicated when certain users are only allowed to change a certain row in a certain kind of way but not in another.
- dllthomas 7y agoI agree, but it does seem to become more compelling if you're doing your integration in the database.
- bayesian_horse 7y agoStill, I think accessing a single database in RDBMs like Postgres or MySQL from multiple codebases or even languages means asking for trouble. Providing some kind of API as a library, REST, RPC or whatever would almost always be preferable, if only to centralize permissions and validation.