Like everything, it depends. Some business logic like "this field should never be negative" is probably fine. More complex logic is a lot harder to maintain.

Like everything, it depends. Some business logic like "this field should never be negative" is probably fine. More complex logic is a lot harder to maintain. You don't want to stress your DB's CPU if you can avoid it. You still need some kind of connection pooler anyway. There's a lot of reasons it doesn't make sense to put all your business logic in the DB. SQL is not the easiest language to maintain (not enough abstraction). IMO the line to draw is just enough to keep data sanity.