Title: I personally think that GraphQL is one of those technologies that has a wide gap in how useful it actually is. For smaller projects it&#x27;s easy to setup, write out your schema, and get going. Likewise, for much larger more complex projects some of the benefits you can get out of GraphQL can warrant the use of it. But there is a massive gap in the middle where it just seems unnecessary.<p>98% of the literature I have seen about GraphQL has always been positive, and it seems to have become the standard recommendation for anything from starting a small web app as a side project, to running a fortune 500 company. I&#x27;m fairly sure that this is because a lot of larger tech companies use GraphQL in some way, so there is this misconception that using it must be the correct choice for all use cases, but who knows.<p>I have worked with GraphQL in a few different companies now, and in all except the largest company where there was a dedicated team of engineers that worked on the GraphQL implementation for the company, I have felt strongly that we would have been better off with a more boring approach like REST.<p>I am curious to hear others perspectives on this, do you like using GraphQL? do you disagree with me and think that it is actually a good solution for the &quot;middle ground&quot; of use cases?<p>Also, I do think that GraphQL has some cool features and I&#x27;m not trying to write it off as a useless tool with no benefits. Like all tools, it has it&#x27;s place but I think that where it&#x27;s really helpful is not where people end up using it in the vast majority of use cases.
Upvote: