The Java Memory Model, Explained Without the Headache
What actually happens to your data between two threads — and the small set of tools that let you control it Ask ten Java developers what “the Java Memory Model” means and you’ll get two different answers. Half of them will draw a box called Heap and another called Stack. The other half will start talking about volatile and happens-before. Both groups are talking about something real, but only the second group is talking about the actual Java Memory Model (JMM). The first group is describing the runtime data areas — where objects physically live. ...