Being the gentle giant: Supporting API users for the long haul

on YouTube ↗19m

" summary

Brightcove’s zencoder team describes concrete fixes: avoid shipping full API keys in client JavaScript (a blog example leaked a read/write key and provoked support cases), prefer server-side API calls, keep integration libraries as thin wrappers to minimize maintenance, and proactively scan recent requests to catch breaking changes (the stricter YAML parser forced testing of month-long activity and targeted emails). Cites practical partners — Stripe, Braintree, Twilio, Filepicker — and an SLA target of about 0.002% monthly downtime as baseline expectations.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 2:00What makes an API good
3. 3:50API abstraction takes control
4. 7:10The problem with quick integrations
5. 8:00Too far beyond your target audience
6. 13:30Providing feedback

" related talks

• 49mAdvanced API design: how an awesome API can attract friends...Jonathan Dahl · RubyConf 2011
• 23mWhat Makes an Agile API?Christian Nilsson · Platform Summit 2014
• 18mUsing APIs appropriatelyErik Eng · Platform Summit 2014
• 15mREST APIs for partners, what’s the catch when applying best practicesKonstantin Yakushev · Platform Summit 2014
• 54mFive-step plan for securing your APIsJavier Garza · AWS re:Invent 2019
• 35mBuilding Your API for LongevityMike Stowe · RubyConf 2014
• 28mMaximize API Growth: Strategies from Industry ExpertsSathyaKhala Anantharajan · apidays Australia 2023
• 43mAPIs Are the Backbone of Every CompanyAnkit Sobti, Marco Wirasinghe, Manian Krish, Børre Wessel · POST/CON 2024