Multiple ChoiceBeginner 45s
API versioning rationale
Why do public APIs typically version via the URL path (e.g. /v2/) or a header?
Options
- 1To reduce payload size, since a shorter path version token trims bytes from every request and speeds up serialization
- 2Because HTTP requires a version identifier in every request, so omitting it from the path or header makes the request invalid
- 3To improve TLS performance, since version-pinned endpoints reuse a single session ticket across all requests from a client
- 4So breaking changes can be rolled out without breaking existing clients that pinned the old contract
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.