Skip to main content

Exchanger in Java's Concurrent API


The Exchanger class in Java's java.util.concurrent package offers a unique synchronization mechanism for concurrent programming. It facilitates exchange of objects between two threads in a pair, acting as a rendezvous point where both threads must arrive with their respective objects before any actual exchange occurs.

Key Concepts:

  • Object Exchange: Each thread presents an object upon calling exchange(). When both threads arrive, they exchange their objects and proceed.
  • Synchronization: exchange() blocks the calling thread until its partner arrives, ensuring data consistency and preventing race conditions.
  • Bidirectional Queue: Consider Exchanger as a two-slot circular buffer where threads take and put items alternatively.
  • Generic Type: Accommodates exchange of objects of any type (T).

Methods:

  • exchange(T object): Exchanges the given object with another thread's and returns the received object. Blocks until another thread arrives.
  • exchange(T object, long timeout, TimeUnit unit): Similar to exchange(), but with a timeout. Throws TimeoutException if the wait exceeds the specified duration.

Common Use Cases:

  • Producer-Consumer: Efficient data transfer between producing and consuming threads, avoiding busy waiting.
  • Pipeline Processing: Implement stages in a processing pipeline where data is passed between stages.
  • Buffer Management: Allocate buffers shared between threads, one waiting for an empty buffer while the other fills it.

Example:

Java
import java.util.concurrent.Exchanger;

public class ExchangerExample {

    public static void main(String[] args) {
        Exchanger<String> exchanger = new Exchanger<>();

        Thread producer = new Thread(() -> {
            try {
                String message = "Hello from producer!";
                String received = exchanger.exchange(message);
                System.out.println("Producer received: " + received);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
        });

        Thread consumer = new Thread(() -> {
            try {
                String received = exchanger.exchange(null);
                System.out.println("Consumer received: " + received);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
        });

        producer.start();
        consumer.start();
    }
}

Additional Notes:

  • Exchanger is generally not suitable for frequent exchanges due to its blocking nature. Consider less disruptive mechanisms for high-performance scenarios.
  • For more complex data sharing patterns, alternative synchronization constructs like BlockingQueue or concurrent data structures might be more appropriate.

Comments

Popular posts from this blog

OWASP API Security Top 10 vulnerabilities 2023

API Security Do's and Don'ts Don't trust input data for an API and do validate all inputs. Ensure you understand security and keep sensitive data out of code. Don't hardcode keys/tokens Don't reveal useful info in error messages. Don't have hidden/unadvertised features. Don't filter data in UI - control at app level Don't confuse authentication and authorization Always use API gateways to control access and traffic Do require API documentation. Do expect users/hackers to find and use undocumented endpoints Do continuous testing - attack simulation, test configs, fuzzing, injections OWASP API Security Top 10 Vulnerabilities 2023 API-1:2023 - Broken Object Level Authorization: BOLA is still the leading vulnerability that plagues APIs. When data objects do not have sufficient access controls in place, resources can be accessed by unauthorized users. API-2:2023 - Broken Authentication  Broken Authentication contains all vulnerabilities associated with auth...

Load Balancer Routing Algorithms - Draft version

The main purpose of the load balancer is to distribute the traffic evenly across multiple servers. The Load Balancer promises the efficient usage of the back-end servers without overloading and not keeping the server in busy times. Avoiding the server overload will reduce the downtime. Table of Content: Different types of LB Algorithms used by ALB ALB Features  Questions Configuring ALB in AWS  Creating K8S config files Factors to consider to ALB design There are different types of load balancers: Application Load Balancer (Layer 7) Network Load Balancer Global Server Load Balancer Let's narrow our discussion to Application Load Balancer(ALB). The ALB operates on layer 7 of OSI model.   Algorithms used by ALB are: Round Robin   Least connections Weighted Round Robin IP hash Least Connections Response time The ALB evaluates incoming requests to ensure efficient and reliable traffic distribution. LB has to ensure. High availability Scalability Performance opt...

React JS Basics

  What are side effects in React? In React, side effects are operations that interact with external systems or cause changes outside the component's rendering process. These can include: Data fetching: Retrieving data from APIs or other sources. Subscriptions: Setting up listeners for events or data changes. Timers: Creating timers for delayed actions or animations. DOM manipulation: Directly modifying the DOM (rarely used in modern React with declarative approach). Why use useEffect ? In class-based components, you would typically use lifecycle methods like componentDidMount , componentDidUpdate , and componentWillUnmount to handle side effects. Functional components don't have these methods directly. The useEffect Hook provides a way to manage side effects in functional components. It allows you to run a function after a component renders (or re-renders) and optionally clean up any resources created by that function before the component unmounts. How does useEffect wor...