GOTO - The Brightest Minds in Tech

Learning API Styles • Lukasz Dynowski & Sam Newman

9 snips
May 1, 2026
Lukasz Dynowski, independent consultant and co-author of Learning API Styles, brings low-level networking insight to API design. He discusses starting APIs from the network layer, choosing protocols and encodings based on context, public vs internal API trade-offs, mixing transports for different traffic, and traits that make APIs usable and maintainable.
Ask episode
AI Snips
Chapters
Books
Transcript
Episode notes
INSIGHT

APIs Need A Network-Level Perspective

  • APIs should be understood from the network up, not just at HTTP/REST level.
  • Lukasz frames APIs by transmission modes (simplex, half-duplex, full-duplex) and sync vs async to expose hidden trade-offs.
ADVICE

Map API Work To An API Development Lifecycle

  • Structure API guidance around an API development lifecycle that maps to SDLC stages.
  • Lukasz split the book: common foundations first, then per-style chapters covering implementation, documentation, trade-offs and retirement.
ADVICE

Design Internal APIs Like Products

  • Treat internal APIs as if they could become public by designing them as products.
  • Lukasz cites the Bezos API mandate as the turning point urging teams to treat APIs as external-grade product contracts.
Get the Snipd Podcast app to discover more snips from this episode
Get the app