It probably does. But at the same time, having a very open protocol can make maintenance hard. Your backend no longer has any idea how it's really being used. There aren't specific APIs to optimize, nor specific unit tests for essential pathways.
While the clients are more flexible you can still check what is accessed together in your monitoring and optimize your resolvers and data-stores for it when needed.
I'd even say that the GraphQL spec (which is stricter than the REST spec) allows for optimizations across different implementations of that spec.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"There's simply no way to be an effective front-end developer and work strictly on code in the "front-end" layer."
I have the feeling solutions like GraphQL change this, by simply giving the front-end more control.
It probably does. But at the same time, having a very open protocol can make maintenance hard. Your backend no longer has any idea how it's really being used. There aren't specific APIs to optimize, nor specific unit tests for essential pathways.
While the clients are more flexible you can still check what is accessed together in your monitoring and optimize your resolvers and data-stores for it when needed.
I'd even say that the GraphQL spec (which is stricter than the REST spec) allows for optimizations across different implementations of that spec.