Give It a REST – Tips for Designing and Consuming Public API’s
summary
Huddle documents a concrete API story: migration to microservices breaks mobile apps until a lightweight Python BFF mimics the old endpoints and lets platforms upgrade gradually; use mini PUT endpoints for single-field updates, return the full resource, and cut multiple HTTP calls into one; enforce a 200 ms performance target, log client IDs to see who still uses old versions, use Last-Modified/ETags, swagger/Postman for docs and testing, 202+polling for long jobs, and 429 rate limits to protect service.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:27What is REST
- 12:09Versioning APIs
- 17:01Defecation
- 21:14User Interface
- 25:39Etags
- 27:04Last Modified Header
- 28:37Too Many Requests
- 29:39Async Pattern
- 31:49Status Property
- 34:44Request Status
- 37:06Android
- 38:59Resources
related talks
57mGive it a REST - Tips for designing and consuming public API's
55mGive it a REST - Tips for designing and consuming public API's
16mDesigning API for Mobile Apps
42mLet’s Have Some Effective REST!
18mUsing APIs appropriately
52mDesigning and Implementing REST APIs For the Long Haul
49mTop REST API Design Pitfalls
01h 39mLet’s have some Effective REST