3 ms·
I don’t think it is - mutations (and state management) are the biggest issue. It’s ok for reads though, although even there tooling for rest is better.
by sheeshkebab 8y ago
I don’t think it is - mutations (and state management) are the biggest issue. It’s ok for reads though, although even there tooling for rest is better.
- RussianCow 8y ago> I don’t think it is - mutations (and state management) are the biggest issue. How so? I don't think GraphQL mutations are any worse than their REST equivalents, especially once you get more complex than "update these fields on this entity".
- lopatin 8y agoI agree with RussianCow, I don't think mutations are in any way harder in GraphQL than they are in REST. IDK what you mean re: state management. That sounds like a client side concern, nothing to do with the protocol used to communicate with the server. Additionally, in my experience, the client-side tooling is better for GraphQL, despite it being around for only a fraction of the time of REST. In fact, that's why I chose GraphQL for my projects. I wanted the tooling (Relay, Apollo) that works out of the box with GraphQL, and requires hacks to get it work with REST.