> It's great for the frontend, but in this case it's awful for the backend.
So what you are saying is it's better to leave this complexity for the frontend developer to handle on the client side? Very wise!
So what you are saying is it's better to leave this complexity for the frontend developer to handle on the client side? Very wise!
And yes, GraphQL makes backend significantly more complex, fragile, and prone to significant performance issues.