Concepts for API Designs
API design concepts are the foundations behind every interface: the main API styles such as REST, GraphQL and RPC, and resource modelling, which means choosing nouns, identifiers and relationships that clients will call. This unit comes first, since naming and structure are the hardest things to change later.
Stage: Principles · Part of the API Design roadmap · Last reviewed 19 November 2026
What to learn in Concepts
- Compare REST, GraphQL and gRPC and pick one for a stated use case
- Model a domain as resources with stable identifiers and clear relationships
- Choose between nested and flat URLs such as /orders/42/items and /items?order=42
- Map create, read, update and delete operations to HTTP methods correctly
- Explain what idempotent and safe methods mean for retries
Concepts interview questions
What makes an HTTP method idempotent?
A method is idempotent when repeating the same request leaves the server in the same state as sending it once. GET, PUT and DELETE are idempotent, while POST usually is not. This matters because clients and proxies can safely retry idempotent calls after a timeout.
When would you choose GraphQL over REST?
GraphQL fits clients that need to shape responses themselves, such as mobile apps with varied screens or many related objects, since one query avoids over-fetching and multiple round trips. REST is simpler for caching, tooling and public resource-style APIs, so the choice depends on client needs.
Where Concepts fits in the API Design roadmap
Concepts belongs to the Principles stage (beginner level), which takes about 20 hours. Think in resources.
Other units in this stage
Back to the full API Design roadmap