|
|
|
|
|
by JonnieCache
4582 days ago
|
|
Ah, so I guess I could stop avoiding traditional SQL features like triggers for fear of having code floating around outside my main app codebase, and it would generally make everything more centralised. I wouldn't have to worry about my workers having access to the correct model code and so on. Interesting. EDIT: how easy do you think it would be to do the authentication etc outside, at the level of the nginx proxy? |
|
For authorization (authz) it's IMHO a bit better to handle it in the DB level, similar with Firebase's ACL lists.