Podcasts

Matthew Skelton and Manuel Pais on Software Architecture, Team Topologies, and Platforms

In this podcast, Matthew Skelton and Manuel Pais, co-authors of the book Team Topologies, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the role of a modern software architect, how team design impacts software architecture, creating “team APIs” in order to reduce cognitive load, and the benefits of building a “thinnest viable platform”.

Pat Helland on Software Architecture and Urban Planning

Wes Reisz talks to Pat Helland about the relationship between software architecture and urban planning. Helland explores planning for future growth, regulations/standards, and communication practices that cities--and software architecture--had to evolve to use. He uses these comparisons to distil lessons that architects can use in building distributed systems.

Yan Cui on Serverless, Including Orchestration/Choreography, Distributed Tracing, & More

Today on the InfoQ Podcast, Yan Cui (a long time AWS Lambda user and consultant) and Wes Reisz discuss serverless architectures. The conversation starts by focusing on architectural patterns around choreography and orchestration. From there, the two move into updates on the current state of serverless cold start times, distributed tracing, and state.

Ana Medina on Chaos Engineering, Game Days, and Learning

In this podcast, Ana Medina discussed with Daniel Bryant about how enterprise organisations are adopting chaos engineering with the requirements for guardrails and the need for “status checks” to ensure pre-experiment system health; how to run game days or IT fire drills when everyone is working remotely; and why teams should continually invest in learning from past incidents.

Stefan Prodan on Progressive Delivery, Flagger, and GitOps

Topics discussed included: how progressive delivery extends the core ideas of continuous delivery; how the open source Flagger Kubernetes operator can be used to implement a progressive delivery strategy via canary releasing with an API gateway or service mesh; and the new “GitOps toolkit” that has evolved from the Flux continuous delivery operator.