DEV Community

Prashant Mishra
Prashant Mishra

Posted on

Proxy

Proxy is one of the structural design patterns, It is used to create a surrogate or placeholder object, which is used to control the access of original object.
It acts as an intermediary adding extra level of control, and can perform extra actions before and after delegating request to real object.

Key Concepts:
Proxy Object: Represents the real object and controls access to it.
Real Object (Subject): The actual object that does the work.
Client: The entity that interacts with the proxy instead of the real object directly.

Lets understand this taking an example of Image.

//Object interface
public interface Image{
    public void display();
}


//Real object
public class RealImage implements Image {
    private String file;

    public RealImage(String fileName){
        this.file = fileName;
        loadImageFromDisk();
    }
    @Override
    public void display(){
        System.out.println("Rendering image : "+ file);
    }
    private void loadImageFromDisk(){
        System.out.println("Loading image "+file+" from disk");
    }
}

//Proxy class
public class ProxyImage implements Image {
    private Image image;
    private String file;

    public ProxyImage(String fileName){
        this.file =fileName;
    }
    @Override
    public void display(){
        if(image ==null){// create object of RealImage only if the image reference is null, thus resulting in LazyIntialization 
            //( i.e. Initializing the object only when it is needed not beforehand)
            image = new RealImage(file);
        }
        image.display();
    }

}

// client
public class Main {
    public static void main(String args[]){
        Image image = new ProxyImage("wallpaper.png");
        //image is loaded and displayed for the first time
        image.display();
        //image will not be loaded again, only display will be called 
        image.display();
    }
}
Enter fullscreen mode Exit fullscreen mode

Output:

Loading image wallpaper.png from disk
Rendering image : wallpaper.png
Enter fullscreen mode Exit fullscreen mode

Use Cases:
Lazy initialization: Delaying object creation until it's absolutely necessary.
Access control: Restricting access to specific methods based on user roles or permissions.
Logging: Adding logging or monitoring functionalities.

Top comments (0)

Great read:

Is it Time to go Back to the Monolith?

History repeats itself. Everything old is new again and I’ve been around long enough to see ideas discarded, rediscovered and return triumphantly to overtake the fad. In recent years SQL has made a tremendous comeback from the dead. We love relational databases all over again. I think the Monolith will have its space odyssey moment again. Microservices and serverless are trends pushed by the cloud vendors, designed to sell us more cloud computing resources.

Microservices make very little sense financially for most use cases. Yes, they can ramp down. But when they scale up, they pay the costs in dividends. The increased observability costs alone line the pockets of the “big cloud” vendors.

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay