I think you should add why and when to use GraphQL. Tools created to solve problem right? Why should I use it when I'm not encounter the same problem like that big company? I'm not Facebook, nor NY Times, maybe sometimes I am, but when?
What REST API cant do and graphQL can? with example?
Yeah it is, but I dont know when to use GraphQL I still dont know why should I add it, I tried once though. But that not a big webapps simple one company profile.
So I really dont know why should I use it. Maybe in big apps thats make difference
I think you should add why and when to use GraphQL. Tools created to solve problem right? Why should I use it when I'm not encounter the same problem like that big company? I'm not Facebook, nor NY Times, maybe sometimes I am, but when?
What REST API cant do and graphQL can? with example?
Some of the mains benefits are:
The GitHub Graph API is a great example of these two benefits. I strongly recommend reading their announcement post.
I think a RESTful API can also reduce the number of API calls in some scenarios. It's not just GraphQL that enables that imo
Maybe Rest can't rise su much VC. 🤔
VC what is that?
VC = Venture Capital
(・o・) (┛◉Д◉)┛彡┻━┻
I think this is the official answer to that.
Yeah it is, but I dont know when to use GraphQL I still dont know why should I add it, I tried once though. But that not a big webapps simple one company profile.
So I really dont know why should I use it. Maybe in big apps thats make difference
I guess when the entities evolve quickly and are interrelated.
Few isolated entities might work better with rest.
I guess it might be also better when you integrate data from different services.