Socio-technical API patterns
summary
Argument: APIs fail or succeed as socio-technical systems, not just code. Shows recurring patterns — Millstone (reluctant internal provider exposes raw data, creating long-term coupling), Rapids with Beaver Dams (API sits mid‑value‑stream, teams drift, consumers build fragile workarounds), and escalation to OpenAPI contract vs reverse‑engineered docs. Recommends bilateral co‑authored contracts, SLAs, API keys, anti‑corruption layers and team merges; notes unilateral design is still the most common practice and usually causes the problems described.
AI-written summary · about
