Java Memory Model in 10 minutes

Java Memory Model is a set of rules all JVMs have to follow to ensure correct working of our concurrent programs.

More resources:

Channel
----------------------------------
Complex concepts explained in short & simple manner. Topics include Java Concurrency, Spring Boot, Microservices, Distributed Systems etc. Feel free to ask any doubts in the comments. Also happy to take requests for new videos.

New video added every weekend.

Popular Videos
----------------------------------

[MEE]

I'm going through this playlist to learn Java concurrency, and I have to say your explanation and presentation quality are amazing, and the diagrams are really helpful.
thank you!

[monishchhadwa]

I would absolutely recommend all Java engineers-whether junior or very senior-to watch this!

[NaturalPro]

The best video i could find on youtube.

[shellindebted]

I tried multiple times myself to understand JMM,
But this is the first time i got to learn something about them.
Excellent Presentation.
Hats of to you, You define perfection!!

[rohitsharma-xtqe]

I have never seen such an excellent explanation of JMM. Thanks a lot

[suhani]

Always read these topic therotically, but could never visualise it like this you have explained..Great presentation man!

[bhavyashah]

Awesome video...Please don't stop making such excellent videos.

[Machinerium]

I had an interview question like that.. This is a very clean explanation, keep doing it!

[iknowyourerightbut]

future me:
volatile has semantics for memory visibility. Basically, the value of a volatile field becomes visible to all readers (other threads in particular) after a write operation completes on it. Without volatile, readers could see some non-updated value.

[Dedeepya]

Started watching thread pool videos Nd then addicted to all of ur videos Nd subscribed..the way of explanation is precise, innovative Nd interesting.your wrk deserves more than a thnks..

[mrchief]

Man, you are awesome. I was struggling trying to understand atomic operations and the use cases of volatile variables. Thank you so much

[tanoysaha]

Your explanations are precise, but have so in-depth/hidden informations and moreover so easy to understand

[Admiral.MacDonnell]

My takeaway - if the tasks perform blocking IO operation, I should not use fork join pool. so true. Thanks for the explanation! You have a gift of mixing complicated concept easy to digest!

[TauCu]

This helped me understand a lot about the JVM Thanks, you're very good at explaining things without any unneeded gibberish!

[skaLife]

You have a good teacher in you. Please continue the good work.

[narendrasriram]

This playlist you have made is too awesome. your example/explanation for happens-before has a few issues. Not sure if I understood wrong, otherwise.Thank you so much for this playslit.

[perrym]

Best explanation I've seen, great work!

[kotojava]

this channel deserve much more subscribers.

[prashanttiwari]

Best video on java on whole YouTube universe

[mostinho]

2:10 each core has its own cache and then there are shared caches. Thread running on core changes the variable in its local cache only, volatile keyword makes sure variable is flushed to shared cache when thread changes it so that changes are visible to all the other threads
6:05 happens before relationship
9:30 volatile keyword example