4 ms·
Hot take: a lot of usage of GraphQL is terrible and most apps don't need it. For example, I worked at a place where it was a requirement that everything runs t
by mcluck 4y ago
Hot take: a lot of usage of GraphQL is terrible and most apps don't need it.
For example, I worked at a place where it was a requirement that everything runs through GraphQL. Sure, fine, except then you see that they were making tailor-made resolvers for particular use cases. You wouldn't see multiple different apps or sections of the app pulling from the same endpoint but with trimmed down queries. It was essentially BFF but with a GraphQL middleware because "it's what big companies do." I've had a number of friends say they've seen the same thing. I'm sure when you're working with applications like Facebook and you're using it intelligently, it's great. My experience is that many people don't understand that.
- eurasiantiger 4y agoI agree, that is a problem: people forget the ”graph” in GraphQL. It’s too easy to just create new query resolver to resolve that one ticket instead of thinking how data relates to other data and how it could be resolved using that other data. That is ultimately a people problem, however: why doesn’t it click that a ”resolver” is intended to ”resolve” other entities based on fields of the parent entity?