Objectives: explain why a stable contract lets teams deploy independently; compare REST, gRPC, GraphQL, WebSocket and messaging and choose one; design a REST resource (URIs, methods, status codes, errors, pagination); tell a breaking change from a compatible one and version when needed; document a Spring Boot service with OpenAPI and Swagger UI and decide where the documentation may be exposed. Outline: (1) the API contract, styles, Richardson; (2) REST API design; (3) OpenAPI and Swagger.
Order API exercise: 201 on create, 400 when an item references a missing product, 404 (not 403) for someone else's order — it does not reveal that the order exists.