Аnother useless writeup for Graphql.. I mean I had to learn it recently. And it is overenginered too complex and tries to do something js is not good and not supposed to do. In rest api I can open a route to give you your contract by id and it is easy.
While in graphql I have to write schema! then I have to write types. Then I have to write the actual query. Not to mention I have to hack it a bit to use more then one query or mutations in one react component for example. And if I want to mutate this contract I have to write a mutation. And if I do it with rest api I just have to open a put request endpoint and that is.
Аnother useless writeup for Graphql.. I mean I had to learn it recently. And it is overenginered too complex and tries to do something js is not good and not supposed to do. In rest api I can open a route to give you your contract by id and it is easy.
While in graphql I have to write schema! then I have to write types. Then I have to write the actual query. Not to mention I have to hack it a bit to use more then one query or mutations in one react component for example. And if I want to mutate this contract I have to write a mutation. And if I do it with rest api I just have to open a put request endpoint and that is.
I am sorry you feel that way (about the writeup not about GraphQL 😁).
GraphQL solves some specific issues but is obviously not a tool to be applied everywhere.
Writing schemas and doing elaborate setup can be minimized by using tools like TypeORM, Prisma, or using a tech-stack like Hasura or PostGraphile.