Summary of 23 gof design modes in one sentence

I. Creation Mode
Abstract Factory: provides an interface for creating a series of related or mutually dependent objects without specifying their specific classes.

Builder: separates components of a complex object from its representation, so that different expressions can be created during the same construction process.

Factory method: defines an interface for creating objects, so that the subclass determines which class to instantiate. Factory method delays the instantiation of a class to its subclass.

Prototype: Use a prototype instance to specify the type of the object to be created, and copy the prototype to create a new object.

Singleton: ensures that a class has only one instance and provides a global access point to access it.

Ii. Structural Mode
Adapter: converts an interface of a class to another interface that the customer wants. The adapter mode allows the classes that cannot work together due to incompatibility of interfaces to work together.

Bridge: separates abstract parts from their implementations so that they can all change independently.

Composite: combines objects into a tree structure to represent a "part-whole" hierarchy. Composite makes the customer's use of a single object and composite object consistent.

Decorator: dynamically add some additional responsibilities to an object. In terms of extended functions, the decorator mode is more flexible than the subclass generation method.

Facade: provides a consistent interface for a group of interfaces in the subsystem. The facade mode defines a high-level interface, which makes this subsystem easier to use.

Flyweight: uses the sharing technology to effectively support a large number of fine-grained objects.

Proxy: provides a proxy for other objects to control access to this object.

Iii. Behavior Model
Chain of responsibility: to cancel the coupling between the request sender and the receiver, multiple objects have the opportunity to process the request. Connect these objects into a chain and pass the request along the chain until an object processes it.

Command: encapsulate a request as an object so that you can parameterize the customer with different requests, queue requests or record request logs, and support cancelable operations.

Interpreter: for a given language, define a representation of its syntax and define an interpreter that uses this representation to interpret sentences in the language.

Iterator: provides a method to access each element of an aggregate object sequentially without exposing the internal representation of the object.

Mediator: uses an intermediary object to encapsulate a series of object interactions. The intermediary removes the need to explicitly reference each other so that the coupling of the device is loose and the interaction between the objects can be changed independently.

Memento: capture the internal state of an object without compromising encapsulation, and save the state outside the object. In this way, the object can be restored to the Saved state.

Observer: defines a one-to-many dependency between objects, so that when the status of an object changes, all objects dependent on it are notified and automatically refreshed.

State: allows an object to change its behavior when its internal state changes. The object seems to have modified its class.

Strategy: defines a series of algorithms, encapsulates them one by one, and makes them replaceable. This mode makes the algorithm changes independent of the customers who use it.

Template Method: defines the skeleton of an algorithm in an operation, and delays some steps to the subclass. The template method allows the subclass to redefine certain steps of an algorithm without changing the structure of an algorithm.

Visitor: an operation that acts on each element in an object structure. It allows you to define new operations that act on these elements without changing the classes of each element.