> This throws away most of what your database can do for you. I personally like to do authorization at the database layer. The whole point of writing maintaina

> This throws away most of what your database can do for you. I personally like to do authorization at the database layer. The whole point of writing maintainable software is to throw away most of what technologies can do, because you are way better off if you do not make the mistake of following that path. For example, at a first glance doing auth at the database layer is a huge mistake. You design your systems with a few nodes having exclusive access to the DB to ensure your access is secure without having to waste the overhead of checking credentials in each db access. The main design trait is speed. But you do you. > There are a tons of other things a DB can do, like trigger a webhook. There are plenty of reasons and hard learned lessons behind principles such as separation of concerns.