Hacker News Reader

Our front end engineers were extremely happy. Me personally, as a backend engineer, not as much, but it isn't too bad.

There are some quirks (error handling), performance issues (e.g. fixing n+1 queries) and DOS concerns, but again, it isn't all that bad.

(we're using rails/graphql-ruby on backend | react/relay on frontend)

View on HN

I'd agree with this sentiment, on the backend, it isn't really easier and it's not really harder either. You end up dealing with different problems than with REST (as noted, different types of performance problems, more issues with error handling have been my biggest two).

The frontend developers see the biggest improvements, they have one endpoint to worry about and using a library like Apollo makes things really nice.

Overall, I think the improvements are worth it, especially when working on internal APIs.

Reply on news.ycombinator.com