We're a place where coders share, stay up-to-date and grow their careers.
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
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.