I. Proxy - Structural Pattern

The Proxy is a familiar Design Pattern for developers, used to represent an original resource. The Proxy provides functionalities similar to the original resource but with high customizability.

The Proxy acts as a substitute for the original resource, hiding complex details or adding necessary features such as access control, caching, or load balancing.

II. Real-world Example

The system frequently needs to query user information from a main database. However, directly querying the main database can increase latency and reduce system performance. Therefore, we use a Proxy that acts as a cache to temporarily store frequently queried data.

The Proxy checks the cache, and if the data exists in the cache, it returns it immediately. Otherwise, it queries the main database and updates the cache.

This use case introduces the mechanism of a Proxy for searching users (User) between the MainDB (main database) and the Stack (cache) to improve performance.

1. Definition of User:

A User only has an ID attribute (int), representing a user entity.

2. Shared Interface:

The UserFinder interface defines the Find(ID int) method to search for a user by their ID. Both MainDB and Stack adhere to this interface.

3. Main Database (MainDB):

The main database where users are stored. UsersDB provides the Find function to search for a user and the Add function to add a new user.

4. Proxy (UserFinderProxy):

The Proxy is a middle layer that uses the Stack (cache memory) for faster access before searching in the MainDB.

• When a User is not in the Stack, the Proxy checks the MainDB.

• If the user is found, the Proxy saves the User in the Stack to optimize subsequent queries.

• The Stack has a capacity-limiting mechanism and auto-updates when full.

The class diagram for the above scenario would be depicted as follows:

III. Implementation

• Definition of the Interface User entity:

1package proxy
2
3type User struct {
4    ID int
5}

• Definition of the Interface:

1package proxy
2
3type UserFinder interface {
4    Find(ID int) (User, error)
5}

• Definition of Database

1package proxy
2
3import "fmt"
4
5type UsersDB []User
6
7func (u *UsersDB) Find(ID int) (User, error) {
8    for _, user := range *u {
9        if user.ID == ID {
10            return user, nil
11        }
12    }
13    return User{}, fmt.Errorf("user not found")
14}
15
16func (u *UsersDB) Add(user User) *UsersDB {
17    fmt.Println("Adding to database: ", user)
18    *u = append(*u, user)
19    return u
20}

• Definition of Proxy:

1package proxy
2
3import "fmt"
4
5type UsersStack []User
6
7func (u *UsersStack) Find(ID int) (User, error) {
8    for _, user := range *u {
9        if user.ID == ID {
10            return user, nil
11        }
12    }
13    return User{}, fmt.Errorf("user not found")
14}
15
16func (u *UsersStack) Add(user User) *UsersStack {
17    *u = append(*u, user)
18    return u
19}
20
21type UserFinderProxy struct {
22    MainDB   UsersDB
23    Stack    UsersStack
24    Capacity int
25}
26
27func (u *UserFinderProxy) Find(ID int) (User, error) {
28    user, err := u.Stack.Find(ID)
29    if err == nil {
30        fmt.Println("Found in stack: ", user)
31        return user, nil
32    }
33
34    user, err = u.MainDB.Find(ID)
35    if err != nil {
36        return User{}, err
37    }
38
39    fmt.Println("Found in mainDB: ", user)
40    u.AddToStack(user)
41    return user, nil
42}
43
44func (u *UserFinderProxy) AddToStack(user User) error {
45    fmt.Println("Adding to stack: ", user)
46    if len(u.Stack) >= u.Capacity {
47        u.Stack = append(u.Stack[1:], user)
48    } else {
49        u.Stack.Add(user)
50    }
51    return nil
52}

• Run the application:

1/*
2    Example Proxy
3*/
4fmt.Println("*** Example Proxy ***")
5
6mainDB := proxy.UsersDB{}
7
8user1 := proxy.User{ID: 1}
9user2 := proxy.User{ID: 2}
10user3 := proxy.User{ID: 3}
11
12mainDB.Add(user1).Add(user2).Add(user3)
13
14proxy := proxy.UserFinderProxy{
15    MainDB:   mainDB,
16    Stack:    proxy.UsersStack{},
17    Capacity: 2,
18}
19
20proxy.Find(1)
21proxy.Find(2)
22proxy.Find(3)
23proxy.Find(2)
24proxy.Find(1)
25
26fmt.Print("*** End of Proxy ***\n\n\n")

With the output:

IV. Explain the example above

This example illustrates how the Proxy pattern works through querying users (User) from the main database (MainDB) while using a stack-based cache (Stack) to optimize repeated search operations. Below is the step-by-step explanation:

1. Initializing the Main Database (MainDB)

1mainDB := proxy.UsersDB{}
2
3user1 := proxy.User{ID: 1}
4user2 := proxy.User{ID: 2}
5user3 := proxy.User{ID: 3}
6
7mainDB.Add(user1).Add(user2).Add(user3)

• A main database (MainDB) is initialized, which holds a list of users (UsersDB).

• Three users with IDs 1, 2, and 3 are added to the MainDB. Any query will be able to find these users if searched directly in MainDB.

Log results:

1Adding to database:  {1}
2Adding to database:  {2}
3Adding to database:  {3}

2. Initializing the Proxy with MainDB and Stack

1proxy := proxy.UserFinderProxy{
2    MainDB:   mainDB,
3    Stack:    proxy.UsersStack{},
4    Capacity: 2,
5}

The UserFinderProxy is created with the following components:

• MainDB: The primary database that stores all the users.

• Stack: A cache layer that is initially empty.

• Capacity: The maximum number of users that the Stack can hold (set to 2 here).

3. Searching for Users

First Search: proxy.Find(1)

1. Proxy checks for ID 1 in the Stack but finds nothing (Stack is initially empty).

2. Proxy switches to searching in the MainDB and finds the user with ID 1.

3. The proxy adds this user to the Stack for faster future queries.

Log results:

1Found in mainDB:  {1}
2Adding to stack:  {1}

Second Search: proxy.Find(2)

1. Proxy checks for ID 2 in the Stack but does not find it.

2. Proxy searches the MainDB, finds the user with ID 2, and adds it to the Stack.

3. The Stack now contains two users: {1, 2}.

Log results:

1Found in mainDB:  {2}
2Adding to stack:  {2}

Third Search: proxy.Find(3)

1. Proxy checks for ID 3 in the Stack but does not find it.

2. Proxy searches the MainDB and finds the user with ID 3.

3. The Stack, already at full capacity (2), operates on a FIFO (First In, First Out) mechanism:
• It removes the oldest user (User with ID 1).
• Then, it adds the new user (3).

4. The Stack now contains {2, 3}.

Log results:

1Found in mainDB:  {3}
2Adding to stack:  {3}

Fourth Search: proxy.Find(2)

1. Proxy checks for ID 2 in the Stack and finds it directly.

2. No need to query the MainDB—the search is instant.

Log results:

Found in stack:  {2}

Fifth Search: proxy.Find(1)

1. Proxy checks for ID 1 in the Stack but does not find it (it was removed earlier).

2. Proxy searches the MainDB and finds the user with ID 1.

3. The Stack, at capacity, removes the oldest user (User with ID 3) and adds the new user (1).

4. The Stack now contains {2, 1}.

Log results:

1Found in mainDB:  {1}
2Adding to stack:  {1}

4. End of Example

Final State:

• Stack: Contains {2, 1} (the two most recently queried users).

• MainDB: Remains unchanged, containing all users {1, 2, 3}.

Final Log:

*** End of Proxy ***

Summary

• For each query, the Proxy first checks the Stack to quickly locate the User.

• If the User is not found in the Stack, the Proxy searches the MainDB and adds the result to the Stack for optimized future searches.

• The Stack has a capacity limit, and when it is exceeded, the oldest User is removed (FIFO – First In, First Out).

Advantages of this approach:

• Reduces the number of accesses to the MainDB when Users are queried repeatedly.

• Improves system performance by utilizing the cache (Stack) for faster lookups.

V. Conclusion

We do not always need to use the Proxy design pattern to address similar problems. In some cases, direct access to the database might suffice if the problem is not complex or performance optimization is not required. In other situations, you might consider using the Decorator pattern or other optimization techniques.

The most important thing is to choose the solution that best fits your specific problem.

Thank you for taking the time to read this article! 😊

VI. References

• Go Design Patterns (Mario Castro Contreras)

• Full source code for Go design patterns: available here.