Interesting observation, because my own experience has been the opposite. With GraphQL I've been able to more easily push business logic to the server.

I disagree, we are using Hasura heavily and most of our business logic is in stateless functions called via db triggers and hasura actions.

It is very easy to provide additional graphql schemas that expose business logic as a remote schema.

My experience have also been the opposite. With GraphQL I can normalize queries and mutations the way it is more fit to the frontend and de-normalize/re-normalize it in the backend.

I'd say it's the opposite. GraphQL allows you to move data fetching and composition logic to the server (resolvers) instead of doing it in the client.

Can you provide more details? I've seen the exact opposite.