(anti)Pattern in REST API design
summary
A practical checklist of REST API anti-patterns and how to fix them: common issues include inconsistent resource URLs (e.g., users vs speakers vs talks), embedding actions in paths like /delete, multipart wizard endpoints that hide state, and storing JSON as strings or using backend-driven field names. Recommended approaches are to use HTTP verbs correctly, prefer shallow JSON structures, set Location and caching headers, use TLS and CORS properly, and add specific endpoints instead of fetching full paginated lists to find single items.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:29APIs deserve attention
- 3:17REST definition
- 5:26URL best practices
- 7:53Input/output formats
- 10:25Serialization antipatterns
- 12:54HTTP headers
- 13:58REST security
- 15:44HTTP semantics
- 17:31State management
- 19:15Response semantics
- 20:17Frontend-backend communication
