Published 1 May 2026
Duration: 00:32:02
This exploration of API design delves into networking fundamentals, communication paradigms, protocol mechanics, trade-offs in security and performance, data formats, microservices communication patterns, emerging technologies like Web Transport and gRPC, and the critical role of secure, documented, and reproducible frameworks aligned with architectural and use-case demands.
This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Lukasz Dynowski - Independent Consultant & Co-Author of "Learning API...
The podcast explores software development through conversations with experts, emphasizing practical lessons, theoretical insights, and strategies for addressing current challenges and innovating. A key focus is on API design, as discussed in the Go To Book Club episode featuring Learning API Styles by Lucas Dynowski. This book redefines API design by examining it through the lens of foundational networking principles (e.g., TCP, OSI model), rather than high-level implementations like REST or gRPC. It delves into API styles at the network layer, contrasting simplex/duplex communication, synchronous/asynchronous frameworks, and protocol-level mechanics. The content bridges theoretical networking concepts with practical implementation examples, such as TCP echo demonstrations, to provide a "360-degree" understanding of APIs for architects and developers. The book also stresses the importance of revisiting foundational principles like RFCs to deepen API comprehension and highlights the interconnectedness of API styles across abstraction layers.
The discussion extends to API development lifecycle considerations, emphasizing reproducibility through resources like code repositories and YouTube tutorials for hands-on implementation. The book is structured around the Software Development Lifecycle (SDLC), mapping API styles (e.g., REST, WebSocket, UDP) to stages like implementation, documentation, and retirement. Trade-offs in API design are contextual, influenced by factors like whether an API is public-facing (requiring security, monetization) or internal. Security, maintainability, and efficiency are recurring themes, with a focus on audience-centric design, backward compatibility, and clear documentation. Practical challenges, such as infrastructure security risks (e.g., RabbitMQs unencrypted storage) and historical shifts like Amazons API mandate, illustrate the real-world implications of design choices. The podcast also touches on emerging trends, including Web Transport for low-latency communication and gRPCs potential in microservices, while underscoring the need for context-driven decisions in protocols, data formats, and communication patterns.
31 Jul 2026 The C4 Model: Visualizing Software Architecture Simon Brown & Susanne Kaiser
The C4 model is a lightweight, structured approach to visualizing software architecture with four levels (System Context, Container, Component, and Code) that prioritizes simplicity, traceability, and effective communication among teams.
17 Jul 2026 Signals & Levers Elisabeth Hendrickson, Joel Tosi & Charles Humble
"Modern software development faces persistent challenges, requiring systems thinking to address dynamic problems, human factors, and cultural shifts beyond Agile and DevOps limitations."
10 Jul 2026 The Architect's Guide to the AI Era Luca Mezzalira & Teena Idnani
"AI accelerates coding and research but requires human expertise for system design, governance, and business alignment, with architects balancing innovation, ethics, and practical constraints to ensure AI augmentsnot replacestraditional engineering."
3 Jul 2026 Model-Based Systems Eng. & Requirements Definition Dennis Hansen & Jorge Orellana
Structured system engineering emphasizes sequential layer development from mission definitions to detailed designs, using documentation (e.g., Technical Requirements Reports, SysML) for traceability, iterative refinement, architecture modeling to manage complexity, and collaboration to align technical and managerial priorities while avoiding parallel component development that causes conflicting requirements.
26 Jun 2026 Sovereign Cloud: Who Really Owns Your Infrastructure? Jake Warner & Charles Humble
The evolution of infrastructure management highlights Kubernetes' limitations, introduces Cycle as a decentralized alternative offering flexible, hybrid deployments and data sovereignty compliance, while addressing cost, vendor lock-in, and geographic data privacy challenges through bare metal use, geographic control planes, and expanded provider support with a free developer tier.