I&#x27;m a big fan of React but it took me a year after its introduction for me to get it and like it. What particularly did the trick for me was one of Pete Hunt&#x27;s talks he gave a year after release acknowledging the confusion and explaining the reasoning for React rather than just the technology itself.<p>I feel like GraphQL can be something great and the pain points they identify with typical APIs are stuff I&#x27;ve felt but GraphQL just feels incomplete to me. I feel they&#x27;re focusing too much on what GraphQL looks like on the client-side and not enough what it looks like on the server-side. The biggest question I have is what&#x27;s going to process the GraphQL query on the server to fetch the data from the actual datastore? What does that look like when working with typical datastore such as a SQL-based database? The closest thing I&#x27;ve seen that answered that question was this blog post[0] which doesn&#x27;t look very appealing if that&#x27;s what the server-side implementation is going to look like. The blog post&#x27;s implementation looks like a more complicated version of my own APIs which are usually a series of custom endpoints based on my client&#x27;s needs. I don&#x27;t see the big deal right now. Maybe next year...<p>[0] <a href="https:&#x2F;&#x2F;medium.com&#x2F;@clayallsopp&#x2F;your-first-graphql-server-3c766ab4f0a2" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;@clayallsopp&#x2F;your-first-graphql-server-3c...</a>