Let me jump right in, the perfect analogy for describing GraphQL is equivalent to what Typescript is to Javascript. In the REST API, payload and end-points are not typed whereas in GraphQL request and response are pre-determined using specified types and we all know the benefits of having typed languages. This is the core principle of GraphQL with other added benefits.
So why is no one talking about GraphQL anymore?
As you can see in the Postman report below, since the release of GraphQL in 2015 the popularity has just grown significantly. And every developer currently has interacted with GraphQL in one way or another. Due to this, almost all of the experienced developers nowadays find GraphQL as part of their career making it no longer a HOT topic of discussion.
Furthermore, like the way Typescript has become a mandatory thing for most Javascript projects. It is sensible to claim that having typed request/response API is going to be a permanent thing in the future.
Now the question is, will GraphQL be the leader in this space or a new technology will emerge, with much simpler implementation than GraphQL?
Learn more about GraphQL in this post -> Why choose GraphQL over REST API?
Top comments (4)
GraphQL is mostly about right-sizing payloads, which isn't a priority for most apps, especially new ones.
It's great for very large APIs that have many consumers, but the majority of developers are working on small and mid-sized apps where REST is ideal.
Yeah that is actually true. It is too much work for smaller to medium size app.
I have always been a big fan of GraphQL but unfortunately it just has not become very popular outside of niche use cases.
Yeah, I have similar thoughts.