You are on the right track using ConcurrentHashMap
. For each point:
- Check out the methods
putIfAbsent
andreplace
both are threadsafe and combine checking current state of hashmap and updating it into one atomic operation. - The get method is not synchronized internally but will return the most recent value for the specified key available to it (check the ConcurrentHashMap class Javadoc for discussion).
The benefit of ConcurrentHashMap
over something like Collections.synchronizedMap
is the combined methods like putIfAbsent
which provide traditional Map get
and put
logic in an internally synchronized way. Use these methods and do not try to provide your own custom synchronization over ConcurrentHashMap
as it will not work. The java.util.concurrent
collections are internally synchronized and other threads will not respond to attempts at synchronizing the object (e.g. synchronize(myConcurrentHashMap){}
will not block other threads).