Proxy pattern represents remote objects locally, this way the local object is used as a proxy of the remote object. The local one can be used in all cases where the remote object is required. The local object can also add some additional functionality/checking while referring to the remote object. This article demonstrates Proxy pattern implementations in Golang.
Flyweight pattern uses a shared object for multiple object generation, which has some common criteria, then populates the different properties while using that object. Using the shared object for generating multiple object output, saves resources and memory usage. This article demonstrates Flyweight pattern implementations in GoLang.
Proxy pattern is used to represent one object(as a proxy) with another object, where we can not use the original object. This is used to represent a remote object or to control access. This article demonstrates Proxy pattern implementations in TypeScript.
Facade pattern adds a new layer on top of any complex subsystem. That way the client does not need to know all the complexity while using the implementation. Facade not necessarily covers all the functionality of the subsystems, only the required functionalities are covered. This article demonstrates Facade pattern implementations in GoLang.
Flyweight pattern uses shared object to save resources and optimize memory use. This article demonstrates Flyweight pattern implementations in TypeScript.
Facade adds a new layer around a bunch of subsystems, and wraps those. Clients interact with the Facade, and are not aware of the systems. This article demonstrates Facade pattern implementations in TypeScript.
Decorator pattern adds new functionality to existing implementation, without changing the existing implementation. The additional functionality is added to individual objects (not to the entire class). This article demonstrates Decorator pattern implementations in TypeScript.
Compsite pattern enables a single object and a list of objects to operate the same way. That way the client does not need to know if it is using a single object or a list, while using it. So the usage becomes simple in that case. This article describes Composite pattern implementation in TypeScript.
Decorator pattern add new functionality to an existing implementation by adding a new layer. The responsibility/functionality is added to individual objects. This article demonstrates Decorator pattern implementations in Go.
Bridge pattern implementation separates the Abstraction and implementation. That way we can switch the implementation at runtime and use the implementation flexibly. This article is about Bridge pattern implementation in TypeScript.