Out of sincere curiosity: Why do you think GraphQL is so bad?
I've been using GraphQL for a little while now and I've had nothing but good experiences (although my use case might not be the most common) so I'm interested in knowing what makes you think so poorly of it.
Not the one you asked, but I'm also stuck with supporting graphql in relatively small project. Zoomers invented SOAP. It's a perfect example of adopting what FAANGS do just for the sake of it. It's probably great when you have dozens of consumers with very different needs and usage patterns. But for the single frontend it adds way too much complexity on the server-side. Debugging, testing, writing tons of boilerate code, not to mention POST requests for getting data - everything becomes more complicated with 0 benefits
In my case, it feels like GraphQL has allowed me to handle a product with very rapidly changing needs without turning our network communication into a gigantic mess with dozens of requests happening for every little thing - which is my previous experience with REST APIs.
Guess it depends on use case. When it's not very clear what your client wants to consume and your product is evolving rapidly, HTTP APIs tend to turn into a mess and lead to a gigantic amount of requests just to start the app (which, to be fair, is less of a problem now with HTTP/3).
GraphQL has allowed my company to keep our network traffic very lean while evolving a product very quickly and to have very few issues in communicating between our mobile application and backend teams. But once again, I can see how our requirements are not everyone else's.
