Operational API design anti-patterns
summary
A GET landing token causes browser caching that breaks kiosk flows so switching to POST fixes it; a Zapier poll every 5 minutes across 90 million forms drives heavy DB load so implementing webhooks replaced polling and a catch‑up polling endpoint migrates ~90% of clients; microservice trees create n+1 latency so a thin BFF (backend-for-frontend) composition API reduces many calls to one; generic action endpoints hide metrics so expose distinct URLs or log actions in query strings for ELK/Kibana visibility.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:16Usability issues
- 6:24Issue: GET Caches
- 6:39Landings: Better
- 12:57Solution: Webhooks
- 15:32Microservices structure: Forms
- 18:56Summary: Rigid resource structure
related talks
37mAPI Horror Stories from an Unnamed Coworking Company
49mTop REST API Design Pitfalls
40mGive It a REST – Tips for Designing and Consuming Public API’s
37mAPI Design: It's Not Rocket Surgery
18mBuild a terrible API for people you hate
41mREST API refactoring.
57mGive it a REST - Tips for designing and consuming public API's
49mPoor API design is not sustainable.