The "scalability issues" for Hashtable are present in exactly the same way in Collections.synchronizedMap(Map) - they use very simple synchronization, which means that only one thread can access the map at the same time.
This is not much of an issue when you have simple inserts and lookups (unless you do it extremely intensively), but becomes a big problem when you need to iterate over the entire Map, which can take a long time for a large Map - while one thread does that, all others have to wait if they want to insert or lookup anything.
The ConcurrentHashMap uses very sophisticated techniques to reduce the need for synchronization and allow parallel read access by multiple threads without synchronization and, more importantly, provides an Iterator that requires no synchronization and even allows the Map to be modified during interation (though it makes no guarantees whether or not elements that were inserted during iteration will be returned).
Here are the differences:
Property |
HashMap |
Hashtable |
ConcurrentHashMap |
Null as a key |
Allowed |
Not Allowed |
Not Allowed |
Is thread-safe |
No |
Yes |
Yes |
Lock mechanism |
N/A |
Locks the whole map |
Locks the portion |
Iterator |
Fail-fast |
Fail-fast |
Fail-safe |
|