> There are HUGE benefits for our client developers with GraphQL. Like being able to select as much or as little as a particular view/component/whatever require

> There are HUGE benefits for our client developers with GraphQL. Like being able to select as much or as little as a particular view/component/whatever requires and no more. That's not a unique benefit of GraphQL. Any HTTP based API can do this, regardless of how it's designed. Some specifications even have it baked in (See: jsonapi.org). > GraphQL from a front end or mobile POV makes your api more like a data store that it can interact with and query for it's needs, which makes app UI work much nicer. Again, not unique to GraphQL. > There are also a ton of maintenance benefits, like for example if you add a field in GraphQL that's perfectly fine to not change the version because that break any existing calls, which is not always true with REST. Again...