Most APIs are designed backend-first, exposing database fields rather than consumer needs. The 'dream query' approach flips this: ask consumers what query they'd write with no constraints, then work backwards to design the schema. This means resolving relationships (returning a Department object instead of a departmentId),

6m read timeFrom wundergraph.com
Post cover image
Table of contents
The Problem With Backend-Out API DesignWhat Is a Dream Query?Working BackwardsWhy Dream Queries Produce Better APIsWho Should Write the Dream Query?A Practical Starting PointFrequently Asked Questions (FAQ)

Sort: