We're a place where coders share, stay up-to-date and grow their careers.
My point here was to show how Graphql can make your work more easier. I also said that Graphql is not always the best solution.
i hear you, it helped me already alot... i usually draw the line at the size of the thing im working at. for small stuff a simple query string to the interface is often enough.
yeah, sometimes it's not appropriate to use GraphQl for small tasks as for REST works well on small tasks.
The title of your article is literally, "4 reasons why you should use GraphQL over REST APIs" and your slug is, "stop-using-rest-for-apis-53n".
Also, GraphQL has many drawbacks, none of which you really mentioned. What about the N + 1 problem? Or having to use and/or implement DataLoader?
In the middle of the post I said that it is difficult to implement caching and that it's not always the best solution.
Some comments have been hidden by the post's author - find out more
My point here was to show how Graphql can make your work more easier. I also said that Graphql is not always the best solution.
i hear you, it helped me already alot...
i usually draw the line at the size of the thing im working at. for small stuff a simple query string to the interface is often enough.
yeah, sometimes it's not appropriate to use GraphQl for small tasks as for REST works well on small tasks.
The title of your article is literally, "4 reasons why you should use GraphQL over REST APIs" and your slug is, "stop-using-rest-for-apis-53n".
Also, GraphQL has many drawbacks, none of which you really mentioned. What about the N + 1 problem? Or having to use and/or implement DataLoader?
In the middle of the post I said that it is difficult to implement caching and that it's not always the best solution.