Immutability by Default: The Foundation of Reliable Systems

"Most introductions to immutability begin with trivial examples. A string is mutated, the result changes, and we are invited to contemplate the danger. But enterprise systems don't fail because someone appended characters to the wrong buffer. They fail because something that was supposed to be a fact - a value that anchored downstream behavior - continued to evolve with the system rather than remaining bound to the moment it was created."

"A system computes a value like price, eligibility, route, risk, entitlement. Other steps depend on that value staying true. Time passes. Business rules change. Deployments diverge across services. Some component updates the original value to reflect the world as it is now. Suddenly, consumers of that value are reasoning about a past that never actually existed. In commerce, this is obvious: A price shown to a customer is overwritten just before checkout. A captured order is retroactively repriced after a promotion expires"

Immutable values act as anchored facts that downstream processes rely on; when those values change, systems experience truth drift. Time, evolving business rules, and divergent deployments cause components to overwrite previously computed values. Overwriting historical values leads to operational inconsistencies, customer-impacting errors, and painful reconciliation. Common examples include prices recalculated after purchase, risk scores reapplied instead of referenced, and workflows resuming with data that no longer matches original intent. Treating computed outcomes as immutable facts — or versioning rules and storing derived values with their context — prevents history from being silently rewritten and preserves predictable behavior.

Read at Medium