Why call one API when you can use GraphQL to call them all?
Why call one API when you can use GraphQL to call them all?

Why call one API when you can use GraphQL to call them all?

Episode publish date
July 4, 2025 4:20 AM (UTC)
Last edit date
Jul 11, 2025 1:20 PM
Last snip date
July 9, 2025 5:11 PM (GMT+1)
Last sync date
July 11, 2025 2:19 PM (GMT+1)
Show

The Stack Overflow Podcast

Snips
13
Warning

⚠️ Any content within the episode information, snip blocks might be updated or overwritten by Snipd in a future sync. Add your edits or additional notes outside these blocks to keep them safe.

Episode show notes

Your snips

[00:45] Matt's Open Source Roots

[01:16] GraphQL's Declarative API Paradigm

[02:30] Complexity of Many APIs

[04:00] Leverage GraphQL Query Planner

[06:16] GraphQL Unifies Complex APIs

[07:47] New York Times Uses GraphQL at Scale

[10:10] Need For Structured AI API Orchestration

[11:19] MCP and GraphQL Synergy

[12:12] GraphQL Fits AI Data Needs

[15:02] GraphQL Solves API Orchestration Challenges

[18:06] Use Nullability for Resilience

[19:17] GraphQL and React Integration

[21:52] Focus on Developer Ergonomics