Summer SALE

Proxy in TypeScript

Proxy is a structural design pattern that provides an object that acts as a substitute for a real service object used by a client. A proxy receives client requests, does some work (access control, caching, etc.) and then passes the request to a service object.

The proxy object has the same interface as a service, which makes it interchangeable with a real object when passed to a client.



Usage examples: While the Proxy pattern isn’t a frequent guest in most TypeScript applications, it’s still very handy in some special cases. It’s irreplaceable when you want to add some additional behaviors to an object of some existing class without changing the client code.

Identification: Proxies delegate all of the real work to some other object. Each proxy method should, in the end, refer to a service object unless the proxy is a subclass of a service.

Conceptual Example

This example illustrates the structure of the Proxy design pattern and focuses on the following questions:

  • What classes does it consist of?
  • What roles do these classes play?
  • In what way the elements of the pattern are related?

index.ts: Conceptual example

 * The Subject interface declares common operations for both RealSubject and the
 * Proxy. As long as the client works with RealSubject using this interface,
 * you'll be able to pass it a proxy instead of a real subject.
interface Subject {
    request(): void;

 * The RealSubject contains some core business logic. Usually, RealSubjects are
 * capable of doing some useful work which may also be very slow or sensitive -
 * e.g. correcting input data. A Proxy can solve these issues without any
 * changes to the RealSubject's code.
class RealSubject implements Subject {
    public request(): void {
        console.log('RealSubject: Handling request.');

 * The Proxy has an interface identical to the RealSubject.
class Proxy implements Subject {
    private realSubject: RealSubject;

     * The Proxy maintains a reference to an object of the RealSubject class. It
     * can be either lazy-loaded or passed to the Proxy by the client.
    constructor(realSubject: RealSubject) {
        this.realSubject = realSubject;

     * The most common applications of the Proxy pattern are lazy loading,
     * caching, controlling the access, logging, etc. A Proxy can perform one of
     * these things and then, depending on the result, pass the execution to the
     * same method in a linked RealSubject object.
    public request(): void {
        if (this.checkAccess()) {

    private checkAccess(): boolean {
        // Some real checks should go here.
        console.log('Proxy: Checking access prior to firing a real request.');

        return true;

    private logAccess(): void {
        console.log('Proxy: Logging the time of request.');

 * The client code is supposed to work with all objects (both subjects and
 * proxies) via the Subject interface in order to support both real subjects and
 * proxies. In real life, however, clients mostly work with their real subjects
 * directly. In this case, to implement the pattern more easily, you can extend
 * your proxy from the real subject's class.
function clientCode(subject: Subject) {
    // ...


    // ...

console.log('Client: Executing the client code with a real subject:');
const realSubject = new RealSubject();


console.log('Client: Executing the same client code with a proxy:');
const proxy = new Proxy(realSubject);

Output.txt: Execution result

Client: Executing the client code with a real subject:
RealSubject: Handling request.

Client: Executing the same client code with a proxy:
Proxy: Checking access prior to firing a real request.
RealSubject: Handling request.
Proxy: Logging the time of request.

Proxy in Other Languages

Proxy in C# Proxy in C++ Proxy in Go Proxy in Java Proxy in PHP Proxy in Python Proxy in Ruby Proxy in Rust Proxy in Swift