One of the main advantages of GraphQL is that you can query for only the data you need. But in order to realize that promise for graph consumers, the schema needs to be thoughtfully designed to support data access requirements for the client apps that will query it. In this workshop, we’ll explore the process of demand-driven schema design and how a “dream query” can be reverse-engineered into a scalable and maintainable GraphQL schema that supports product use cases. What you’ll learn: Common schema design patterns Build queries to display the data your app needs Best practices for designing client-focused queries Practical tips for schema reviews Federation / composite schemas considerations