Java Concurrency In Practice

Abstract

To address the abstraction mismatch between Java's low‐level mechanisms and the necessary design‐level policies, we present a simplified set of rules for writing concurrent programs. Experts may look at these rules and say "Hmm, that's not entirely true: class C is thread‐safe even though it violates rule R." While it is possible to write correct programs that break our rules, doing so requires a deep understanding of the low‐level details of the Java Memory Model, and we want developers to be able to write correct concurrent programs without having to master these details. Consistently following our simplified rules will produce correct and maintainable concurrent programs.