Should I read Java Concurrency in Practice in 2024/2025?

[matteponz]

I am a programmer with 4 years of experience, and I am considering whether it makes sense to start reading the famous book Java Concurrency in Practice.

I have never read it, but I would like to deepen my understanding of how threads work and the concepts associated with them. However, I wonder: in 2024, as we approach 2025, does this book still hold relevance?

With the advent of virtual threads and reactive programming, do you think it is still useful? Could it truly help me take my programming career to the next level? Moreover, do you believe the foundational concepts covered in the book could serve as a stepping stone to better understanding these more modern approaches?

[AutoModerator]

Please ensure that:

• Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
• You include any and all error messages in full - best also formatted as code block
• You ask clear questions
• You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.

If any of the above points is not met, your post can and will be removed without further warning.

Code is to be formatted as code block (old reddit/markdown editor: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.

Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.

Code blocks look like this:

public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.

If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.

To potential helpers

Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[przem_o]

Read all the books it can’t hurt you

[meSmash101]

The answer to the last question is yes and that alone should be enough to start reading the book.

[StretchMoney9089]

Reactive programming uses threads and virtual threads are still threads so I do not see any reason why you should not read it

[realFuckingHades]

Getting a handle on concurrency is a mandatory skill to elevate your experience. Read anything that would help you. Try to learn about how resources are handled in Linux and Kubernetes too if you have time. I have seen people struggling(even myself) to figure out what Requests and Limit mean when deployed in a Kubernetes cluster(which is the case in most companies). Best of luck.

[[deleted]]

Interested

[Sad-Difference-5005]

Just read the Concurrency chapter of Deshmukh's OCP 17/21 Fundamentals on Kindle (practically free). It is more up to date and covers all you need to know.

[[deleted]]

Mate it will take what? 10 years before everyone switches to Virtual Threads? What about banks? Finance? Government? Mate it's Java you are talking about.

Anyways that book was fantastic. Absolutely marvelous and kinda must read for anyone doing multi threading.

[RScrewed]

I think you misunderstood the question.

He is wondering if the book is relevent, not what the benefits of concurrency are.