Graphql go

What’s this so well know graphql? Go’tcha, I won’t discuss about this at all LoL. Take a look in those articles below: https://www.moesif.com/blog/technical/graphql/REST-vs-GraphQL-APIs-the-good-the-bad-the-ugly/ https://blog.logrocket.com/why-you-shouldnt-use-graphql/ https://www.apollographql.com/docs/react/data/operation-best-practices/ https://graphql.org/ https://www.youtube.com/watch?v=epKhPB9PJqY&ab_channel=Simplilearn But, personally, what I think about it: Good points: It can be interesting when the amount of data of each request is relevant (mobile/lightweight apps) It can be interesting doing to the reuse of existent resolvers for our types (you’ll see an example in this project) It’s easier to the backend developer to handle with the errors (without worring about status codes, padronized response bodies and go on) It’s interesting to have a panel where you can see all available types/queries/mutations and its descriptions Bad points: