GraphQL vs. REST
Sashko Stubailo

What would you say to the REST biased dev, who says, REST has HATEOAS and thus can offer a discoverable and state generating/ controlling/ directing API, where GraphQL doesn’t have this notion of “navigation through state”. I think that would make for a good comparison point too.

Another comparison point is caching. Since REST uses HTTP, it can cache a lot of responses directly with standard cache systems. Since GraphQL can offer very unique responses, cache becomes more complicated. Where does GraphQL pick up the slack in this area?


One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.