What does the programming mode mean?

The PHP programming pattern is first and foremost a singleton pattern, which allows only one object of a certain class to be created. The constructor private defines a static getinstance method in which an instance of the object is created. If the instance already exists, it is not created.

For example, you only need to create a database connection. Then there's the factory pattern, the factory method, or the class that generates the object, instead of directly new in **. Using the factory pattern, you can avoid changing the name or arguments of a class in all the **s that call the class.

Enrollment mode that addresses global sharing and exchanging objects. The objects that have been created can be hung on an array that can be used globally, and when you need to use it, you can get it directly from the array. Registers the object with the global tree.

Go straight to visit anywhere. A policy pattern that encapsulates a specific set of behaviors and algorithms into classes to suit certain contexts. In observer mode, when the state of an object changes, all objects that depend on it will be notified and automatically updated.

I hope I can help you! If my answer is helpful to you, please give a thumbs up (comment in the lower left corner), look forward to your like, your efforts are very important to me, your support is also the motivation for my progress, and finally I wish you good health and a happy mood!

Design patterns are one of the means of architecture.

Specifically, design patterns can help architect the static structure of software in some cases.

The scope of the architecture is larger, higher-level, and more important global design decisions. A generally good (static) architecture allows changes to occur locally (within modules) as much as possible without affecting the entire system. Architectural changes tend to be very costly.

And only some of the design patterns are for architecture, some are just for specific class design, and the rest are just for overcoming the limitations of programming languages.

To use an inappropriate analogy, it's a bit like the relationship between pick-and-roll and tactics.

In the right situation, good blocking and dismantling can be a good execution of tactics, but tactics are not only blocking and dismantling, and some tactics do not need to block and dismantle, and the most important thing is that blind blocking and dismantling can sometimes be counterproductive.

In the face of customer beep, we use the requirements analysis architecture.