Counterpoint: think of your database server as any other microservice, with an API. Putting a limited amount of logic there can vastly increase (not decrease) t

Counterpoint: think of your database server as any other microservice, with an API. Putting a limited amount of logic there can vastly increase (not decrease) the overall application performance. One can also use stored procedures and views to allow the model to change while maintaining backwards compatibility with other services. Alternatively, don't use SQL at all, and use a NoSQL database where you can't put any logic at all. If you aren't going to use the power of the database, then don't "pay" for it.