4 ms·
Has GraphQL cracked role based data fetching patterns? I would love to learn those patterns..
by itsbits 5y ago
Has GraphQL cracked role based data fetching patterns? I would love to learn those patterns..
- steve76 5y agoI use next-auth, relay-nextjs, and jwt on PostGraphile: https://www.graphile.org/postgraphile/jwt-guide/ https://www.graphile.org/postgraphile/jwt-guide/
- jrsj 5y agoAs someone who works on multi tenant systems where accidentally crossing boundaries would result in millions of dollars in fines…yeah I would like to see more examples of this in particular haha
- aniforprez 5y agoWhat about caching? I'm not sure I like my frontend libraries trying to solve caching when I could very easily get that incredibly simply for free with REST and browser or endpoint caching. I'm really hard pressed to find proper examples that describe auth, RBAC, UBAC, caching etc with GraphQL When it first came about it seemed like a band-aid to try and get around poorly designed REST systems so backend engineers wouldn't have to deal with frontend devs asking for data and new endpoints. I dunno if it's matured enough past that. Not saying REST is perfect and lord knows enough companies abuse it but a lot of stuff is pretty solved with simple, well documented solutions online