Legacy Software and Immutable Infrastructure with Chad Fowler

CaSE: Conversations about Software Engineering

Joy Clark talks with Chad Fowler about legacy software and immutable architecture

• Website
• Immutable Architecture
• The Passionate Programmer
• From Homogeneous Monolith to Radically Heterogeneous Microservices Architecture
• Kill “Microservices” before it’s too late
• Impermanence as the key to good systems thinking
• Wunderlist
• A3 Outage

Chapters

1. Introduction (00:00:00)

2. How long does it take for a piece of software to be considered legacy software? (00:02:47)

3. Is it a given that my application will need to be replaced? (00:03:36)

4. Should we try to create code that can be reused? (00:09:06)

5. Services vs. Libraries (00:13:20)

6. How can we ensure that small services do not become dependent on each other? (00:16:35)

7. How can we test a system composed of hundreds of different services? (00:18:41)

8. How can we ensure that a system itself doesn't become monolithic and difficult to replace? (00:21:50)

9. Immutable Architecture at Wunderlist (00:24:27)

10. What is immutable infrastructure? (00:29:04)

11. Can immutable infrastructure be used within a cloud company? (00:35:34)

12. Is there a risk to basing your whole system on Docker? (00:39:00)

13. How can we apply the concepts of immutable architecture to software development? (00:41:20)

14. If someone is getting started as a software developer, what should they focus on? (00:47:19)