4 ms·
With GraphQL and single page apps, people tend to move their business logic to the frontend side. I am not sure it is a good idea seeing how moving are the fron
by vmaurin 6y ago
With GraphQL and single page apps, people tend to move their business logic to the frontend side. I am not sure it is a good idea seeing how moving are the frontend tech
- andrewingram 6y agoInteresting observation, because my own experience has been the opposite. With GraphQL I've been able to more easily push business logic to the server.
- dudul 6y agoCan you provide more details? I've seen the exact opposite.
- meiraleal 6y agoMy 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.
- jensneuse 6y agoI'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.
- diveanon 6y agoI 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.