3 ms·
> the author doesn't mention is that you can limit the set of queries clients can call in a GraphQL service, by hash or signature. Then it's just REST with ext
by troupo 2y ago
> the author doesn't mention is that you can limit the set of queries clients can call in a GraphQL service, by hash or signature.
Then it's just REST with extra steps and none of the benefits
- nielsole 2y agoAs this is being downvoted can someone explain why this wouldn't be true? One of the core tenets of graphql was not having to involve the backend team, wasn't it?
- akshayshah 2y agoIn places I've seen this used, front-end developers can run any query in development environments. In production (and sometimes staging) environments, queries must be allowlisted. This gives the front-end developers lots of flexibility when initially developing new screens and components. Once the UI is ready to ship, the backend team checks to make sure that performance is acceptable (optimizing if necessary), allowlists the new query/queries, and ships to production.