It's really a question of what stack gets the responsibility for organizing an operation. If it's the front-end then yes, GraphQL is the proper choice. But I've found it places unnecessary burden on front-end, and extra work on the service that would otherwise be better spent in other areas. Allowing front-end engineers to work on REST API is the obvious solution. Breaking down walls and instilling confidence in our engineers is key to success, IMO. Nice article.
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.
It's really a question of what stack gets the responsibility for organizing an operation. If it's the front-end then yes, GraphQL is the proper choice. But I've found it places unnecessary burden on front-end, and extra work on the service that would otherwise be better spent in other areas. Allowing front-end engineers to work on REST API is the obvious solution. Breaking down walls and instilling confidence in our engineers is key to success, IMO. Nice article.