Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
ajit555217781dAssuming you must have already done GraphQL vs REST API analysis.
gitpush3503981d@ajit555 yup and from what I've found is that main difference is flexibility in fetching data, so that we can define our own response instead of having to write an endpoint for it.
But what I'm still not able to learn, role based fetching? Like if I'm a regular user I can only fetch, for example, books. But if I'm an author, then I can fetch my book sales and only my book by finding out who am I from the token I provide and not by passing my Id to the query
ajit555217781d@gitpush I had a quick review of GraphQL, it is in my TODO to go deeper once need arise.
My suggestion is irrespective of what GQL server you use later, for learning, pick one which has a great resource on documentation, YouTube tutorials, code examples. I think Apollo GQL is a very good one to start with.
Now, read on authentication and authorization section in Apollo documentation and go from there:
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job