GraphQL is a great way for FE devs to make life harder for BE devs. The entire point is composition + client customization of the response body, but in practic

GraphQL is a great way for FE devs to make life harder for BE devs. The entire point is composition + client customization of the response body, but in practice the request schema is never modified. And even if it were, you could just version a REST endpoint. GraphQL is never done "correctly," adds a layer of obscurity to monitoring and error tracing, and I've yet to see a case where it's actually the right tool for the job. Maybe if you need to aggregate calls to multiple services into one, but if you're trying to avoid latency by reducing number of calls, you still eat that latency while the GraphQL server makes those calls for you. GraphQL sucks.