Scope an agent's part in a GraphQL migration
Your task
Leadership wants your REST API moved to GraphQL, and suggests pointing an agent at the OpenAPI spec to generate the whole schema and every resolver. You have 80 endpoints and real production traffic. Mobile clients on old app versions will keep calling REST for at least a year.
How do you scope the agent's work and sequence the migration so nothing breaks?
It covers
- Rest to graphql
- Scoping
- Strangler