API Design

REST vs GraphQL: decide by consumer shape

• REST by default — single web app, simple CRUD-shaped resources, straightforward client needs.
• GraphQL when there are multiple/diverse consumers (e.g. mobile + web hitting the same backend with different data needs) where flexible querying avoids either over-fetching or a proliferation of purpose-built REST endpoints.
• Don't default to GraphQL for a single-consumer CRUD app just because it's more capable — the extra schema/resolver machinery isn't earning its cost there.

REST resource design