At the risk of sounding like an evangelist: if it’s slowing you down, you may be doing it wrong. If you are hand-crafting interdependent query logic to resolve

At the risk of sounding like an evangelist: if it’s slowing you down, you may be doing it wrong. If you are hand-crafting interdependent query logic to resolve GraphQL queries from multiple sources and doing that at scale, you may want to look at db adapters and the federation pattern. Also, GraphQL absolutely still requires error handling in the frontend, and many clients actually provide great facilities for error handling: retrying failed requests, refreshing auth tokens transparently on received auth errors, network state detection, offline functionalities, etc.