Skip to main content

Concurrent Collection Classes:

Concurrent Collection Classes:

Java utility classes are generally useful when used with concurrent programming. This package includes a few small standardized extensible frameworks and some classes that provide proper functionality that is otherwise very difficult to implement.


Concurrent Collections:

This package supplies Collection implementations mainly used in multithreaded processes. A concurrent collection is always thread-safe, and a single exclusion lock does not govern it.


Here are some of the classes below:

  • ConcurrentSkipListMap: Usually preferable to a synchronized TreeMap

  • CopyOnWriteArraySet: Well suited for applications where set sizes generally stay small and read-only operations vastly outnumber mutative operations(add, set, remove, etc.).

  • ConcurrentSkipListSet: This is essentially an equivalent of TreeMap and TreeSet for concurrent code.

  • CopyOnWriteArrayList: It’s preferable over synchronized ArrayList, where an expected number of reads vastly outnumbers the number of updates in the list.

  • ConcurrentHashMap: Whenever many threads are expected to access a given collection, ConcurrentHashMap usually is preferable to a synchronized HashMap.

Popular posts from this blog

Executer vs ExecuterSevice: What's the Difference?

Executer and ExcuterService: Executor and ExecutorService are part of Java's Executor framework, which provides  thread pool  facilities to Java applications. Since creating and managing Threads are expensive, It's a better idea to create a thread pool that can execute in parallel rather than every time a new thread is requested, helping reduce the load. This improves the response time of the application. Differences between Executer and ExecuterService: One of the key differences between the Executor and ExecutorService interface is that the former is a parent interface while ExecutorService extends Executor.  A second significant difference between ExecutorService and Executor is that Executor defines an execute() method, which accepts the Runnable interface object. Simultaneously, a submit() method takes both Runnable and Callable object interfaces. Another difference between Executor and ExecutorService interface is that the execute() methods' return type is void, wh...
Read more

Atomic operation and classes in the Java Concurrency API:

Atomic Operation and Class: An operation is classified as atomic if it is performed as a single unit of work without the possibility of interference from other processes. In the Java language specification, they guarantee that the reading or writing operation is atomic (unless the variable is a long or a double). Variables of type long or double in operations are only atomic if declared with the keyword: volatile. Suppose we assume that  i  is defined as an int. The  i++  (increment) operation is not an atomic operation in Java. This also applies to the other numeric types, e.g. long.  This is because the  i++  operation first reads the value currently stored in  i , and then it adds one to it. However, between the read and the write, the value of  i  might have changed. Since Java 1.5, the java language provides an atomic class with variables such as AtomicInteger or AtomicLong. The class also provides methods like getAndDecrement(), ge...
Read more