// module
GraphQL Integration Studio
AUD 890 (informational)
Responsible mentor
Jonah Reeves
API workshop lead; previously embedded with product squads.
Outcomes
- Ship a versioned schema proposal teammates can comment on
- Demonstrate one batching win with numbers
- List three trade-offs between REST and GraphQL for your product
Description
You maintain a schema changelog, write resolver tests, and document N+1 risks. The capstone pairs with a mocked partner team to mimic awkward field requests.
Inside the track
- Schema review rituals with annotated diffs
- DataLoader patterns and batching exercises
- Persisted query discussion (pros/cons)
- Client cache invalidation scenarios
- Load testing scripts with readable thresholds
- GraphQL security checklist walkthrough
Reviews
The schema changelog format from GraphQL Integration Studio is now how we argue about fields without shouting.
Batching lab was finicky; worth it. Still slower than I want on cold starts — noted in retro.
FAQ
We standardise on one server and one client stack for the cohort, announced before kickoff. Concepts transfer.
Comfortable REST and basic SQL. If SQL is shaky, take Postgres for Builders first.
Federation at scale is overview-only; no multi-month platform programme inside this block.