~/talk

Backend API Design for SREs

Talkat SREcon22 Asia/Pacific · 2022-12-07..12-09· [api-design, distributed-systems]

speaker

name:Sam Dunster

links:none on file

resources

video:https://youtu.be/i7zbiRAEKgs

slides:none on file

summary

Good backend API design reduces operational toil and prevents false SLI drops by using clear error classes, predictable IDs, and client-friendly flows. Use nanoid for short high-entropy IDs and enable autocompletion with two characters so tracing and debugging across services is fast. Decide sync vs async up front (aim for async if operations can exceed 30 seconds), return operation IDs for polling, map 4xx vs 5xx for SLIs, document valid ID/name combinations, and dogfood the API via a CLI and integration tests.

AI-written summary · about

chapters (6)

related talks