Failure atomicity

In traditional programming, failure in one thread can easily affect the other one. As immutability enforces low coupling, the internal state of the application will be consistent, even when we have exceptions on any module/thread.

The reason is simple, the immutable objects never change state. So, even if failure occurs in one part/module/thread, it stops right there and doesn't get any chance to get spread to other parts of the application.