InfoQ Homepage The InfoQ Podcast Content on InfoQ
-
Why Rust Will Help You Deliver Better Low-latency Systems and Happier Developers
Andrew Lamb, a veteran of database engine development, shares his thoughts on why Rust is the right tool for developing low-latency systems, not only from the perspective of the code’s performance, but also looking at productivity and developer joy. He discusses the overall experience of adopting Rust after a decade of programming in C/C++.
-
Is WebAssembly the Secure, Efficient Alternative Everybody was Waiting for?
Laurent Doguin and Geoffroy Couprie discuss their pioneering work with Wasm on the infrastructure side. They walk us through the benefits and challenges of building a platform over WebAssembly and why it’s the safer alternative to containers.
-
Continuous Deployment and Pair Programming for Lean Software Delivery Even without Jira
Asgaut Mjølne Söderbom and Ola Hast, two developers with Sparebank1, speak about their journey towards continuous deployment and pair programming. During the conversation, they share how they use the "waste clock" to identify areas of improvement or how TDD helps them deliver high-quality code.
-
Sovereign Clouds, Hyperscalers and European Alternatives: InfoQ Dev Summit Munich 2025 Preview
In this podcast episode, speakers from the upcoming InfoQ Dev Summit Munich 2025 tackle the practical challenges facing European developers caught between regulatory pressures and technological realities. The panel discusses trade-offs between using US cloud providers versus emerging European alternatives, exploring cloud-agnostic architecture strategies and the implications of data sovereignty.
-
The Financial Architecture of Software with Ian Miell
In this episode, Thomas Betts speaks with Ian Miell about how the financial aspects of a business affect how software is designed and built. If Conway’s Law says organizational structures determine the software design, then following the money helps us understand why those organization structures exist, and ultimately whether software will be successful in achieving its goals.