InfoQ Homepage The InfoQ Podcast Content on InfoQ
About this Podcast
Intended for architects and senior developers.
-
Removing the Dependency of Zookeeper on Kafka
Today on the InfoQ Podcast, Wes Reisz talks with Justin Gustafson and Colin McCabe , two of the engineers currently working on removing the dependency of ZooKeeper in Kafka. The three discuss why the team made this decision, what the ramifications are, and explore what both the near and future state will be with upgrading and operating Kafka.
-
Asim Aslam on Microservices, go-micro, and PaaS 3.0
In this podcast, Asim Aslam, founder and CEO of Micro, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: microservices vs functions; the go-micro and micro frameworks; and the evolution of PaaS and how the new M3O platform fits into the landscape.
-
Anne Currie Discusses Cloud Providers and the Environmental Impact of Software
Charles Humble talks to Anne Currie from Container Solutions, exploring the environmental impact of technology. They look at how technology compares to other industries such as aviation and farming, how the big cloud providers compare in terms of their commitments to reducing carbon emissions, and the impact of the choices made by individual developers and software architects.
-
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.
