I Thought GraphQL Was the API. It Turned Out to Be the Orchestration Layer.

Before I first touch GraphQL in production, I thought GraphQL was simply “REST but with better querying.”

After implementing a concession capture feature, I realised GraphQL is really an orchestration layer sitting between consumers and downstream services.

A few things finally clicked:

• GraphQL usually exposes a single endpoint
• Queries and mutations define behaviour, not URLs
• Schemas are executable contracts, not documentation
• GraphQL often wraps existing REST services rather than replacing them
• A seemingly simple schema change can ripple through resolvers, codegen, tests and downstream integrations

The feature itself wasn’t particularly difficult. The interesting part was discovering that GraphQL often isn’t the destination. It’s the traffic controller sitting in front of everything else.