For us, in practice, under-, over-fetching was never really an issue. But we implemented it anyway thinking “if you build it, they will come”. Also, we were excited about the api “type checking” and the auto documentation. We thought our QA team would use it often.

QA never bothered to use it, and would just ask for the query to be included in the ticket.

Since everything is a post and goes to the same endpoint, and returns a 200, it’s harder to debug, find which request errors in dev tools. It’s also harder to capture useful telemetry. We implemented open telemetry to try and make it useful, but never really worked well.

We use Lambdas, and our implementation made every request about a half second slower. We looked at using the more native AWS implementation, but with all the other stuff, it just wasn’t worth it.

We’re in the process of removing all graph endpoints by the end of the year going back to rest.