Software Engineering Radio - the podcast for professional software developers

Software Engineering Radio - the podcast for professional software developers

Download on the App Store

Software Engineering Radio - the podcast for professional software developers episodes

  • SE Radio 230: Shubhra Khar on NodeJS

    Shubhra Kar of StrongLoop talks to Jeff Meyerson about Node.js. Node allows for server-side JavaScript. Shubra and Jeff explore why Node is so important from three standpoints: isomorphic JavaScript, the single-threaded-concurrency model, and the "API economy." Isomorphic JavaScript apps have their own control and viewing logic, but they share the state and specification of the models between client and server. Node's single-threaded event loop concurrency model is ideal for Web programming, where time is traditionally wasted while waiting on I/O. The API economy is dominated by JSON (JavaScript Object Notation), which Node treats as the first-class data model. Shubhra also discusses the changing landscape of the client-server model in a conversation about Browserify, which creates a directory structure in the browser, allowing for conflict management between client and server. Other topics discussed include MongoDB, model-driven development, and V8.

    58 min
  • SE Radio 229: Flavio Junqueira on Distributed Coordination with Apache ZooKeeper

    Flavio Junqueira is the author of Zookeeper: Distributed Process Coordination. Flavio and Jeff Meyerson begin by defining ZooKeeper and talking about what ZooKeeper is and isn't. ZooKeeper can be thought of as a patch against certain fallacies of distributed computing: that the network is secure, has zero latency, has infinite bandwidth, and so on. With ZooKeeper, a programmer can be insulated from these problems or at least have a tool to better manage them. More concisely, ZooKeeper is a coordination kernel. It's a set of primitives that abstracts away coordination, leader election, and other troublesome aspects of maintaining a distributed system. Flavio also discusses scaling ZooKeeper, the CAP theorem, and contrasting distributed tools such as Chubby.

    50 min
  • SE Radio 228: Software Architecture Sketches with Simon Brown

    Simon Brown, author of Software Architecture for Developers, talks with Sven Johann about using simple sketches to visualize, communicate and document software architecture. The show starts with a consideration of why sketches are more useful than UML and then continues with the explanation of the C4 model (context, containers, components and classes) and how it fits Shneiderman's mantra. Next Brown discusses why the code never matches the diagrams, how frameworks are guilty of this, and what you can do to let the code scream the architecture at you. Finally, it's all about how to create a useful documentation which can also easily maintained and browsed.

    57 min
  • SE Radio 227: Eric Brewer: The CAP Theorem Then and Now

    Robert Blumen talks with Eric Brewer, who discovered the CAP (consistency, availability, partition tolerance) theorem. The first part of the show focuses on Brewer's original thesis presented at the 2000 ACM Symposium on Principles of Distributed Computing (PODC): What set of problems motivated the formulation of CAP? How was it understood at the time? What are the three types of systems that can exist (or are there only two types)? Is latency the same as a partition? The second half of the show covers Brewer's more recent retrospective article on how things have changed since then: What major insights about CAP have emerged? How has CAP impacted the architecture of real applications? How can architects use the full space of the CAP theorem to arrive at the best designs? Are some types of systems more CAP-friendly? How do CAP systems recover when partitions are healed? The show wraps up with some speculation about the next 16 years.

    46 min
  • SE Radio 226: Eric Evans on Domain-Driven Design at 10 Years

    Eberhard Wolff talks with Eric Evans, the founder of domain-driven design (DDD), about its impact after 10 years. DDD consists of domain-modelling patterns; it has established itself as a sound approach for designing systems with complex requirements. The show covers an introduction to DDD, how the community's understanding of DDD has changed in the last 10 years, the often overlooked component—strategic design, how to use DDD to design microservices, and the connection between microservices and the DDD bounded context. DDD originated during the era of object orientation and relational databases; the show concludes with a look at the recent impact of functional programming and NoSQL on DDD.

    55 min
  • SE Radio 225: Brendan Gregg on Systems Performance

    Senior performance architect and author of *Systems Performance* Brendan Gregg talks with Robert Blumen about systems performance: how the hardware and OS layers affect application behavior. The discussion covers the scope of systems performance, systems performance in the software life cycle, the role of performance analysis in architecture, methodologies for solving performance problems, dynamic tracing and tracing tools such as DTrace, the disk and file subsystems, the CPU and memory subsystems, and the challenges virtualization poses for performance analysts.

    1 hr 1 min
  • SE Radio 224: Sven Johann and Eberhard Wolff on Technical Debt

    In this episode, Sven Johann and Eberhard Wolff talk about technical debt and how to handle it. They begin by defining external and internal quality and then talk about technical debt as a metaphor for discussing quality with management. They then consider whether technical debt is bad and how to handle it by using Eric Evan's strategic design. The show explores the reasons for technical debt; Martin Fowler's quadrant model is good for categorizing the root causes. Approaches to handling technical debt include the radical question of whether technical debt should be repaid at all. After all, debt-free systems actually might not exist, which leads to the question of whether technical debt is a good metaphor. Quality investments based on the SQALE (Software Quality Assessment based on Lifecycle Expectations) provide a different metaphor and another way to handle technical debt.

    57 min
  • SE Radio 223: Joram Barrez on the Activiti Business Process Management Platform

    Josh Long talks to Activiti cofounder Joram Barrez about the wide world of (open source) workflow engines, the Activiti BPMN2 engine, and what workflow implies when you're building process-driven applications and services. Joram was originally a contributor to the jBPM project with jBPM founder Tom Baeyens at Red Hat. He cofounded Activiti in 2010 at […]

    1 hr 3 min
  • SE Radio 222: Nathan Marz on Real-Time Processing with Apache Storm
    Nathan Marz is the creator of Apache Storm, a real-time streaming application. Storm does for stream processing what Hadoop does for batch processing. The project began when Nathan was working on aggregating Twitter data using a queue-and-worker system he had designed. Many companies use Storm, including Spotify, Yelp, WebMD, and many others. Jeff and Nathan […]
    58 min
  • SE Radio 221: Jez Humble on Continuous Delivery
    Johannes Thönes interviews Jez Humble, senior vice president at Chef, about continuous delivery (CD). They discuss continuous delivery and how it was done at Go, CD, and HP firmware; the benefits of continuous delivery for developers; Conway's law and cross-functional teams; scary releases and nonscary releases; fix-forward, blue-green deployments, and A/B testing; origins of continuous […]
    1 hr 6 min

About Software Engineering Radio - the podcast for professional software developers

From the publisher's feed

Software Engineering Radio is a podcast targeted at the professional software developer. The goal is to be a lasting educational resource, not a newscast. SE Radio covers all topics software…