My use graphql in production. The ideas are good but think it not worth it. schema is nice, but I would love to build an app with fastify + swagger is a piwerful combination.
Graphql does not deliver on its promise against overfetching. What I observe, is that frontend developer take the complete type definition and fetch everything in one go.
and it needs a huge shift in the mindset of developers. in rest and graphql alike, I observe that APIs get implemented specifically for separate pages.
Often I think graphql is more something for personalized data. With rest there are very good tools for caching like varnish that cache the hell out of your rest api apps. but not so much with graphql.
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.
My use graphql in production. The ideas are good but think it not worth it. schema is nice, but I would love to build an app with
fastify+swaggeris a piwerful combination.Graphql does not deliver on its promise against overfetching. What I observe, is that frontend developer take the complete type definition and fetch everything in one go.
and it needs a huge shift in the mindset of developers. in rest and graphql alike, I observe that APIs get implemented specifically for separate pages.
Often I think graphql is more something for personalized data. With rest there are very good tools for caching like
varnishthat cache the hell out of your rest api apps. but not so much with graphql.