Virtual Proxy Pattern in Java: Enhancing Performance with Lazy Loading Techniques

About 3 min

Also known as

Lazy Initialization Proxy
Virtual Surrogate

Intent of Virtual Proxy Design Pattern

The Virtual Proxy Design Pattern is a crucial component in Java design patterns, enabling efficient resource management and performance optimization through controlled object creation. It provides a surrogate or placeholder for another object to control its creation and access, particularly when dealing with resource-intensive operations.

Detailed Explanation of Virtual Proxy Pattern with Real-World Examples

Real-world example

Just as a high-end art gallery uses photographs to save resources and reduce risks, the Virtual Proxy Pattern in Java manages resource-intensive operations by displaying only necessary objects, significantly enhancing system efficiency. To protect the actual artwork and reduce the risk of damage or theft, the gallery initially displays high-quality photographs of the artworks. When a serious buyer expresses genuine interest, the gallery then brings out the original artwork from a secure storage area for viewing.
In this analogy, the high-quality photograph serves as the virtual proxy for the actual artwork. The real artwork is only fetched and displayed when truly necessary, thus saving resources and reducing risk, similar to how the Virtual Proxy pattern defers object creation until it is needed.

In plain words

The virtual proxy pattern allows a representative class to stand in for another class to control access to it, particularly for resource-intensive operations.

Wikipedia says

A proxy that controls access to a resource that is expensive to create.

Programmatic Example of Virtual Proxy Pattern in Java

The Virtual Proxy design pattern in Java can optimize resource utilization and system performance.

Consider an online video streaming platform where video objects are resource-intensive due to their large data size and required processing power. To efficiently manage resources, the system uses a virtual proxy to handle video objects. The virtual proxy defers the creation of actual video objects until they are explicitly required for playback, thus saving system resources and improving response times for users.

Given our example of a video streaming service, here is how it might be implemented:

First, we define an ExpensiveObject interface, which outlines the method for processing video.

public interface ExpensiveObject {
    void process();
}

Here’s the implementation of a RealVideoObject that represents an expensive-to-create video object.

@Slf4j
@Getter
public class RealVideoObject implements ExpensiveObject {

    public RealVideoObject() {
        heavyInitialConfiguration();
    }

    private void heavyInitialConfiguration() {
        LOGGER.info("Loading initial video configurations...");
    }

    @Override
    public void process() {
        LOGGER.info("Processing and playing video content...");
    }
}

The VideoObjectProxy serves as a stand-in for RealExpensiveObject.

@Getter
public class VideoObjectProxy implements ExpensiveObject {
    
    private RealVideoObject realVideoObject;

    public void setRealVideoObject(RealVideoObject realVideoObject) {
        this.realVideoObject = realVideoObject;
    }

    @Override
    public void process() {
        if (realVideoObject == null) {
            realVideoObject = new RealVideoObject();
        }
        realVideoObject.process();
    }
}

And here’s how the proxy is used in the system.

public static void main(String[] args) {
    ExpensiveObject videoObject = new VideoObjectProxy();
    videoObject.process();  // The first call creates and plays the video
    videoObject.process();  // Subsequent call uses the already created object
}

Program output:

14:54:30.602 [main] INFO com.iluwatar.virtual.proxy.RealVideoObject -- Loading initial video configurations...
14:54:30.604 [main] INFO com.iluwatar.virtual.proxy.RealVideoObject -- Processing and playing video content...
14:54:30.604 [main] INFO com.iluwatar.virtual.proxy.RealVideoObject -- Processing and playing video content...

When to Use the Virtual Proxy Pattern in Java

Use the Virtual Proxy pattern when:

Object creation is resource-intensive, and not all instances are utilized immediately or ever.
The performance of a system can be significantly improved by deferring the creation of objects until they are needed.
There is a need for control over resource usage in systems dealing with large quantities of high-overhead objects.

Virtual Proxy Pattern Java Tutorials

The Proxy Pattern in Java (Baeldung)

Real-World Applications of Virtual Proxy Pattern in Java

Lazy Initialization: Create objects only when they are actually needed.
Resource Management: Efficiently manage resources by creating heavy objects only on demand.
Access Control: Include logic to check conditions before delegating calls to the actual object.
Performance Optimization: Incorporate caching of results or states that are expensive to obtain or compute.
Data Binding and Integration: Delay integration and binding processes until the data is actually needed.
In Java, the java.awt.Image class uses virtual proxies to load images on demand.
Hibernate ORM framework uses proxies to implement lazy loading of entities.

Benefits and Trade-offs of Virtual Proxy Pattern

Benefits:

Reduces memory usage by deferring object creation.
Can improve performance by delaying heavy operations until needed.

Trade-offs:

Introduces complexity in the codebase.
Can lead to unexpected behaviors if not handled properly, especially in multithreaded environments.

Proxy: Virtual Proxy is a specific type of the Proxy pattern focused on lazy initialization.
Lazy Loading: Directly related as the core idea of Virtual Proxy is to defer object creation.
Decorator: Similar in structure, but Decorators add behavior to the objects while proxies control access.