Immutable Infrastructure, Immutable Code - The Phoenix ArchitectureIn 2013, I wrote about trashing servers and burning code. The argument was simple: systems that mutate while running accumulate state, history, and uncertainty in ways humans can't reason about. When something breaks, nobody knows which change caused it or what the system actually is anymore. So we stopped patching servers and started replacing them. We built machines that could burn down and rise
