Uniformity ain't all bad getting consistent behavior across your API
summary
Concrete techniques and failures: code shows a centralized standard criteria layer for consistent query params, an override render to pass options pattern for tidy serializers and per-client detail levels, and a RESTful batch approach implemented as a batch_api rack middleware gem (sequential execution, potential for parallelism). Examples include the Koala double JSON encoding bug and an executable docs/test harness, plus opinions on single-format JSON, strict output, migration-style versioning. Watch if working code and gotchas matter.
AI-written summary · about
chapters (17)
- 0:00Start
- 4:21Facebook Describes the App Restrictions Api
- 9:08Expect Consistent Behavior
- 10:36Code Smell
- 10:51Api Smell
- 16:09Pseudo Code
- 17:20Sending Back the Data to the User
- 17:39Tour of Render
- 20:04Managing Global Behavior
- 21:36Bonus Chapters
- 22:08Batch Api
- 23:21Example To Change Themes
- 25:24Final Summary
- 26:14How Do You Approach Api Versioning
- 28:57Why Did You Not Use Http Pipelining for the Badge Requests
- 29:56Do You Do any Documentation Generation from Your Apis
- 30:12Executable Documentation
