you show some differences, between rest and graphql, and I also like your analogies.
In practice I had other experience. I find the frondend engineers do the overfetching themselfs. by putting fragments if queries together. querying more data then actually shown. The single endpoint is a nightmare for caching. The varnish cache is great for working with varying URLs, with different post data not so much. So caching solutions have to move into the appserver itself.
As a backend developer, I still continuously have frontend engineers asking for API's in very specific usecases, needed on only one page, with no way to use it well in other situations.
While you can build good successful projects with graphql, I don't see it as much better than Rest API.
Thanks for sharing your perspective! I'm still learning about GraphQL, so it's interesting to hear from someone with more day-to-day experience. It sounds like there are tradeoffs, like when choosing any technology. And of course room for user error 😂
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
you show some differences, between rest and graphql, and I also like your analogies.
In practice I had other experience. I find the frondend engineers do the overfetching themselfs. by putting fragments if queries together. querying more data then actually shown. The single endpoint is a nightmare for caching. The varnish cache is great for working with varying URLs, with different post data not so much. So caching solutions have to move into the appserver itself.
As a backend developer, I still continuously have frontend engineers asking for API's in very specific usecases, needed on only one page, with no way to use it well in other situations.
While you can build good successful projects with graphql, I don't see it as much better than Rest API.
Thanks for sharing your perspective! I'm still learning about GraphQL, so it's interesting to hear from someone with more day-to-day experience. It sounds like there are tradeoffs, like when choosing any technology. And of course room for user error 😂