The Architect is not Convinced
summary
Architects refuse blanket promises and want specifics: the four concrete objections are control, reliability, security, longevity and each needs a concrete counter. Show a client library and an escape hatch (Orchestrate uses Lucene query syntax and supports bulk export), publish machine-readable status pages with response-time and error-rate graphs (Stripe, Twilio, GitHub examples), prove data-access and privacy processes, and admit risk—remember one in three Google APIs are gone—then describe the business model that sustains the API.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:30API Providers
- 3:55Four Areas to Convince the Architect
- 6:44Biggest Competitor
- 7:45Standards Conventions
- 11:11Exporting Data
- 12:25Fail Whale
- 13:05Twitter Downtime
- 14:57Twitter Status Page
- 16:35GitHub Status Page
- 17:02Security
- 19:08Data Ownership
- 19:44Longevity
- 21:49API Business Model flowchart
- 23:46API Longevity
related talks
41mArchitecture decision making
45mArchitecture: The Stuff That's Hard to Change
01h 01mAn Architect's Approach to API Strategies
16mBuilding Future-Proof API Platforms
29mDefence in depth
44mDeliberate Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
49mWhy software architects fail: and what to do about it