Ask HN: Anyone move from GraphQL back to rest?

17 points·sergiotapia··11 comments

Interested in hearing stories of organizations who went from graphql back to REST.

View on HN

I’m not even at “rest” let alone “graphql” ... more like create a motley bunch of endpoints via http!

I feel ya

I see the drive to GraphQL from REST for some SAAS and think its a mistake.

I find REST is much easier to use - I read the docs and look at one or two examples then I can get started

GraphQL is a different story - Im hunting round the documentation to figure out the syntax and rules.

I much prefer REST

I can see no reason to go back unless you did it badly - maybe you'd support both if you exposed apis to end users - REST is easier to grok initially.

https://www.graphiti.dev/guides/why

How is this relevant?

It’s literally a library that’s main value proposition is that GraphQL loses a lot of benefit of web http infrastructure that rest provides and that with a few conventions you get many of the most widely cited values of GraphQL.

I haven’t left GraphQL myself, but after seeing what’s necessary to expose GraphQL for consumption, it’s very clearly an attractive waste of time.

After having worked on a codebase with it, I would prefer RESTful endpoints backed by RDBMS or document stores instead.

Hey, I created this thing: https://graph-4d1ec.firebaseapp.com/

I feel the same pain and end up built a library to try to solve it. https://github.com/charlie0077/graphql-server-crud

We're using gRPC.

Reply on news.ycombinator.com