Yes, You Should Provide a Client Library For Your API
summary
Claim: shipping a client library measurably improves safety, security, readability, and developer happiness, especially for concerns like auth, retry, batching and instrumentation. Organization-scale proof: several hundred public APIs get maintained with generators. Tools and formats: OpenAPI and protobuf/gRPC plus OpenCensus for traces. Implementation lesson: metaprogramming prototypes lead to obscure stacks so teams switch to code generation instead of metaprogramming to emit real Ruby gems and docs, avoiding integration pain that otherwise saved weeks of integration for consumers.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:43Google Cloud Platform
- 5:36Is it worth it?
- 9:50Caching
- 12:40Know the protocol
- 27:58Metaprogramming
- 29:42Code generation
related talks
30mAPI Design Matters
35mI want to publish my first Open Source library
43mBuilding a Ruby Library the Parts No One Talks About
22mBuilding the Great Wall: API Driven Applications
28mThe New API Stack
15mOptimizing API Integration in a Large React Application Using OpenAPI Generator
35mOpensource API Tools to agile your apifirst strategy.
52mFireside chat on client libraries