Immutability in Clojure

In Clojure, immutability is not “a best practice”. It is the default. When you “change” a vector or map, you get a new value back, and the old one is still valid.

The key idea that makes this practical is structural sharing: the new collection reuses most of the old collection’s structure instead of copying everything.

What to internalize early

• Use assoc, update, conj, dissoc to produce new values.
• Do not look for setters. Data is just data.
• Keep mutation at the edges (interop, I/O, state coordination).

Java mental model: final references and unmodifiable collections are optional in Java. In Clojure, “no in-place mutation” is built into the standard data structures.

Once you trust immutability, many other Clojure idioms become obvious: concurrency is safer, tests are simpler, and refactors have fewer hidden coupling points.

In this section

• Why Immutability Matters
  See why immutable values reduce hidden coupling, preserve snapshots, and make concurrent JVM systems easier to reason about.
• Immutable Data Structures in Clojure
  Learn how Clojure's vectors, maps, sets, and lists behave, and how updates create new values without in-place mutation.
• Structural Sharing and Performance
  Understand why immutable updates stay practical on the JVM, and when transients are the right optimization tool.