Cache objects as Immutable classes

Question

I am asking very generic question and the answer can vary from requirement to requirement, but for "general" or "rule of thumb", can we say the following is a good design rule:

The classes to be cached (static/reference data) should be designed as immutable, with exceptions reasoned.

What could be design/performance issues with the above statement, if this is not true?

Answer 1

@JohnB has a good answer about the underlying data.

If, however, the question is referring to the immutability of the cached classes themselves (which are holding the data in the cache), then the answer is that mutable classes can cause thread-safety issues if the instances of the classes are referenced by multiple threads (as can often happen with data shared via a cache). Additionally, "accidental" modification of the data may occur, where a shared instance is unintentionally modified (because the modifying code did not know that the data was shared).