Designing APIs: Less Data is More

on YouTube ↗25m

" summary

Designs a minimal blogging platform (authors, posts, comments) and claims smaller APIs save real work: exposing an email field forces deprecation cycles and client coordination, adding a reviewer relationship creates N+1 and performance costs, making update-comment accept a post_id invents unsupported UI flows, and omitting pagination limits becomes a scaling bug. Advocates schema-first, iterative delivery, redundant fields elimination and a strict to loose policy so additions are cheap and removals avoid breaking clients.

AI-written summary · about

" chapters (6)

1. 0:00Introduction
2. 3:03Dont expose redundant fields
3. 7:06Dont expose redundant relationships
4. 11:53Dont expose redundant input fields
5. 15:30Avoid extra flexibility
6. 18:36Defensive programming

" related talks

• 24mBuild The API FirstRosie Hoyem, Sonja Hall · RailsConf 2014
• 35mBroken APIs Break Trust: Tips for Creating and Updating APIsAlex Wood · RailsConf 2018
• 32mRefactoring Legacy Apps with APIs and MessagesCorey Ehmke · LoneStarRuby Conf 2013
• 42mLightweight Web ServicesBlake Mizerany, Adam Wiggins · RubyConf 2008
• 44mDesigning Hypermedia APIsSteve Klabnik · RailsConf 2012
• 38mDesigning a Great Ruby API - How We're Simplifying Rails 5Sean Griffin · RailsConf 2015
• 33mUniformity ain't all bad getting consistent behavior across your APIAlex Koppel · Barcelona Ruby Conference 2012
• 17mDesigning software that maximizes developer productivityKirsten Westeinde · The Lead Developer New York 2019