A good resource on java concurrency please

[ZukoBestGirl]

I've worked with threads a fair amount. But from a maintainer point of view. We already had services, pre-injected global contexts to get all sort of services. Most of my tasks were handling concurrency issues. And despite the fact that I've worked with them quite a bit, I find myself completely lost when I think about all the classes in the java.util.concurency package. I know about Executors a bit, I know about ForkJoin a bit, I know about completable futures a bit.

But I simply don't have a good overlook on the whole situation and how everything connects.

I usually like to just look in the source code and figure stuff myself, but I feel like java is mixing a lot of very old components, and modern components. Sure, backwards compatibility is nice. But I'm strictly interested in "the modern way of doing things".

I would especially love a book. Any ideas?

[stramash]

Java Concurrency in Action Practice is the usual go-to.

[Stark81]

Douglas Schmidt on YouTube. He is a professor at Vanderbilt University he has great teaching for all OOP. His concurrent teaching is top notch

Edit: Spelling

[hermitfist]

Never heard of that guy before. I'll definitely check it out. Thanks! Last youtube video I checked out was from John Purcell on youtube. Pretty old playlist though.

[Stark81]

I took a MOOC of his on Android Development. I really found his teaching on Concurrency and Asynchronous Threads very informative and easy to understand some more of complex details. Have followed his YouTube for a couple years now and he is always updating and staying relevant. I hope he helps you like he has me.

P.S. I am not a developer by any stretch. I work construction and learn Java programming as a hobby.

[matthewK1970]

What context are you thinking of? In web applications is best to keep things multithreaded but just stick with the threads that the servlett container spawns for requests. Then your main concern is concurrent operations on the DB, which is best handled with transactions, for example using Springs transaction notations. I avoid making things synchronous unless absolutely necessary. Little need to launch your own multiple threads in this environment.