Thanks for the response. Indeed, there are a couple times in the article where I nod to the fact that GraphQL isn’t a magic bullet. In fact, if your application doesn’t have the performance or complexity requirements of the Facebook news feed, you’re probably fine with REST.

I think you bring up some fair points in your article. Overall, however, GraphQL is just a spec for fetching data. It’s up to the developer to implement it effectively and efficiently. AND to make decisions about whether GraphQL is right for their use case.

Agreed that many companies adopting GraphQL right now might not need it really, and they’re probably making things more complicated and slower by doing so poorly or without the proper backend engineering to support it.