Since its introduction by Facebook, GraphQL has swept the world as an alternative to REST APIs. GraphQL fixes many issues that API developers and users find in RESTful architectures. But it also poses a new set of challenges to overcome. GraphQL is ...
Markdown supported · ⌘↵ to post
Another article saying rest has no way to limit the data. There are tons of ways to do this, the API you are using as an example chose NOT to implement any. OData had a way to limit data, even pass query params, join info, etc. This is not new.
GraphQL is not magic, someone still had to implement the API to do the query the right way, etc. You can do the same and expose a REST and GraphQL endpoint that do the same things.
Lucky victory
Full-stack Software Engineer
Great article, but my question is, when exactly is GraphQL a better option to REST? In what kind of applications are they mostly needed? Social media apps or Blogs?