InfoQ Homepage Continuous Delivery Content on InfoQ
-
Dave Farley on Continuous Delivery
Dave Farley discusses the reasons for Continuous Delivery and Continuous Deployment, the advantages and challenges they pose, and much more.
-
Rachel Laycock on Continuous Delivery
Rachel Laycock explains her experience with bringing Continuous Delivery to companies, the main technical and social obstacles, and much more.
-
Alex Papadimoulis on Delivering Web Scale Systems
Alex Papadimoulis shares his thoughts on distribution vs delivery, decoupling infrastructure (pull) from application (push) deployments and keeping delivery systems simple, especially for web scale applications. In particular Alex describes three different types of roll-outs: Live, Rolling and Parallel and their applicability (cloud-based delivery vs in-house servers).
-
Michael Nygard - Redefining CAP
In this InfoQ interview, Michael Nygard explores some of the available loopholes in the CAP theorem helping architects to engineer distributed systems that meet their needs. He also discusses new patterns he’s observed since his book, Realease IT and shares his thoughts on continuous delivery, DevOps and ALM.
-
Jeff Sussna on Continuous Delivery, Cloud Journey and AWS Momentum
IT thought leader Jeff Sussna answers a range of questions about operational efficiency and cloud trends. He discusses new thinking around production freezes and adopting continuous delivery. Sussna explains how companies should understand the entire lifecyle of a customer’s cloud experience. Finally, he shares insight into AWS and their leading position in the cloud.
-
Adrian Cockcroft on Architecture for the Cloud
In this interview we talk with Adrian Cockcroft, the architect for Netflix’s cloud systems team. We discuss how Netflix combines 300 loosely coupled services across 10,000 machines. An interesting revelation is that they fully embrace continuous delivery and each team is allowed to deploy new versions of their service whenever they want.
-
Continuous Delivery and the Four Principles of Low-Risk Software Releases
More than a year since his book Contiuous Delivery came out, author Jez Humble talks about changes in CD, and its relationships with Cloud development, ALM. He also shares his Four Principles Of Low-Risk Software Releases. Other topics include TDD, feedback at different stages of the pipeline, and his involvement with Devops.
-
Peter Bell on the State of Java, Managing Software Development Teams, Startups
Peter Bell discusses the state of Java today and whether startups are using it or not, polyglot programming, startups in New York, how to keep up to date with technology, and much more.
-
Techniques for Disciplined Agile Delivery
Based onconcepts presented in his book, Scott Ambler describes Disciplined Agile Delivery (DAD) as a hybrid approach that extends Scrum, Agile modeling, Unified Process. DAD is a people-first process that's goals-based rather than prescriptive, addresses the entire lifecycle and shares many concepts presented in continuous delivery. Scott also discusses the DevOps movement and how DAD addresses it
-
Henrik Kniberg on Lean From The Trenches, Translating the Agile Manifesto and Living Agile
Henrik Kniberg discusses the journey to writing his latest book "Lean from the Trenches", the translation of the Agile Manifesto as well as his recent travels and Lean Startup projects.
-
Jim Highsmith on Adaptive Leadership
Recorded at the 10th anniversary of the agile manifesto signing, Jim Highsmith discusses how he works with executive management teams to introduce and integrate agile techniques into enterprise organizations from both the business and IT sides. He defines adaptive leadership and discuses adaptive ALM, continuous delivery, lean and Kanban methods.
-
Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches. Jesper also discusses the benefits of integrating elements of Kanaban into existing Scrum teams and what can be achieved from the team seeing the entire value chain and owning the whole process.
