![]() ![]() I have seen many programmers who simply weren't able to visualize how multiple threads are interacting with the same piece of code and different data. There's no doubt that multi-threading and concurrency are difficult they are both hard to get it right in code and hard to understand and explain. It also goes on to explain why most concurrent applications are incorrectly written in Java and the common mistakes made by Java programmers, which result in multi-threading issues like race conditions, deadlock, livelock, memory interference, and simply incorrect calculation.Įmoticons are used to show the bad practice before introducing the good and/or right way to do it, not only to correct the misconception many Java developers had before but to sow the seed of correct information pertaining to multi-threading and concurrency among Java developers. ![]() visibility, ordering, thread-safety, immutability, parallelism, etc. The most important thing this book introduces is clear concepts and fundamentals of concurrent programming, e.g. Many Java developers will tell you that this book has become a bit dated in 2019, but my view is slightly different from most, and I still recommend Java Concurrency in Practice to any new Java developer or intermediate developers who want to master concurrency concepts. The book offered them the seamless introduction of those tools and how they can use them to write high-performance concurrent Java applications. ![]() CountDownLatch, CyclicBarrier, ConcurrentHashMap, and much more. Many Java programmers were even not aware of new tools introduced in the API, e.g. I think this was the first big attempt to improve Java's built-in support for multi-threading and concurrency. When this book was first published in 2006, the Java world was still not sure of about new concurrency changes made in Java 1.5. One of my readers, Shobhit, asked this question on my blog post about must-read advanced Java books: is the book " Java Concurrency in Practice" still relevant? I really liked the question and thought many Java programmers might have similar thoughts whenever someone recommends this popular Java read. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |