InfoQ Homepage Architecture & Design Content on InfoQ
-
Michelle Noorali on the Service Mesh Interface Spec and Open Service Mesh Project
In this podcast, Michelle Noorali, senior software engineer at Microsoft, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the service mesh interface (SMI) spec, the open service mesh (OSM) project, and the future of application development on Kubernetes.
-
Stephen Wolfram on Computer Language Design, SMP, Mathematica, and Wolfram Language
In this episode of the InfoQ podcast, Charles Humble talks to Stephen Wolfram about Wolfram Language, its origins and the influences on its creation. In a wide-ranging discussion they also cover the ergonomics of programming languages; Wolfram|Alpha’s integration with Siri, Alexa, and the upcoming integration with Microsoft Excel; and live streaming language design discussions via Twitch.
-
Andrew Clay Shafer on Three Economies, the Wall of Confusion, and the Origin of DevOps
Wes Reisz speaks with one of the people at the center of the creation of the idea of DevOps. Andrew Clay Shafer is the VP of transformation at Red Hat where his role is about helping companies change their relationship with software in the cloud native ecosystem. On the podcast Shafer talks about the Three Economies, Wall of Confusion, and a bit about those first mentions of DevOps.
-
Alois Reitbauer on Cloud Native Application Delivery, Keptn, and Observability
In this podcast, Alois Reitbauer sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the goals of the CNCF app delivery SIG; how cloud native continuous delivery tooling like Keptn can help engineers scale development and release processes; and the role of culture change, tooling, and adopting open standards, such as OpenTelemetry, within observability.
-
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.