Design pattern simple factory
Design Patterns After the previous article about the singleton pattern, I finally want to continue writing. Let’s start with the simplest one, the simple factory pattern. This design pattern is very simple and the most commonly used (isn’t it the same with many things? , the simpler, the lower the threshold and the more likable it is).
Concept (forgive me for shamelessly copying Baidu Encyclopedia):
The simple factory pattern is a creational pattern, also called the static factory method (Static Factory Method) pattern, but it does not belong to the 23 types of GOF One of the design patterns. The simple factory pattern uses a factory object to determine which product class instance is created. The simple factory pattern is the simplest and most practical pattern in the factory pattern family and can be understood as a special implementation of different factory patterns.
What is said here is very clear. A factory has N objects. This is the essence of a simple factory. The specific UML class diagram is as follows
First download the online tool Processon. This is my invitation link. Of course, if you need to draw a lot of pictures, please spend money to support them.
Let’s explain this class diagram. It consists of three parts. One is Creator, which is the factory class, the second is the IProduct interface, and the third is the specific products A and B.
The specific code is as follows
Product interface:
public interface IProduct {void meathod(); }
Specific product:
public class ProductA implements IProduct {public void meathod() { System.out.printf("产品A"); } }
public class ProductB implements IProduct {public void meathod() { System.out.printf("产品B"); } }
Factory:
public class Creator {public static IProduct createProduct(String productName) {if (null == productName) {return null; } else if ("A".equals(productName)) {return new ProductA(); } else if ("B".equals(productName)) {return new ProductB(); }return null; }public static void main(String[] args) { IProduct productA = Creator.createProduct("A"); productA.meathod(); IProduct productB = Creator.createProduct("B"); productB.meathod(); } }
Output: Product A Product B
Specific example:
Such a simple model is relatively common. Take our project as an example. The products we make use various interfaces from multiple partners. Most of the interfaces are the same, but the specific fields and details are different. , for example, when applying for credit, all you need is some personal privacy information. What each company wants is roughly the same, but individual information is different. This is very suitable for the factory model.
Advantages and disadvantages:
Advantages: decoupling, helping encapsulation.
Disadvantages: Increases the complexity of the client, which is not conducive to expanding sub-factories
In fact, the essence of the simple factory pattern is to choose to implement it.
Let’s just say this and so much.
The above is the detailed content of Design pattern simple factory. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

In the Java framework, the difference between design patterns and architectural patterns is that design patterns define abstract solutions to common problems in software design, focusing on the interaction between classes and objects, such as factory patterns. Architectural patterns define the relationship between system structures and modules, focusing on the organization and interaction of system components, such as layered architecture.

The Adapter pattern is a structural design pattern that allows incompatible objects to work together. It converts one interface into another so that the objects can interact smoothly. The object adapter implements the adapter pattern by creating an adapter object containing the adapted object and implementing the target interface. In a practical case, through the adapter mode, the client (such as MediaPlayer) can play advanced format media (such as VLC), although it itself only supports ordinary media formats (such as MP3).

The decorator pattern is a structural design pattern that allows dynamic addition of object functionality without modifying the original class. It is implemented through the collaboration of abstract components, concrete components, abstract decorators and concrete decorators, and can flexibly expand class functions to meet changing needs. In this example, milk and mocha decorators are added to Espresso for a total price of $2.29, demonstrating the power of the decorator pattern in dynamically modifying the behavior of objects.

1. Factory pattern: Separate object creation and business logic, and create objects of specified types through factory classes. 2. Observer pattern: allows subject objects to notify observer objects of their state changes, achieving loose coupling and observer pattern.

Design patterns solve code maintenance challenges by providing reusable and extensible solutions: Observer Pattern: Allows objects to subscribe to events and receive notifications when they occur. Factory Pattern: Provides a centralized way to create objects without relying on concrete classes. Singleton pattern: ensures that a class has only one instance, which is used to create globally accessible objects.

The advantages of using design patterns in Java frameworks include: enhanced code readability, maintainability, and scalability. Disadvantages include complexity, performance overhead, and steep learning curve due to overuse. Practical case: Proxy mode is used to lazy load objects. Use design patterns wisely to take advantage of their advantages and minimize their disadvantages.

The Guice framework applies a number of design patterns, including: Singleton pattern: ensuring that a class has only one instance through the @Singleton annotation. Factory method pattern: Create a factory method through the @Provides annotation and obtain the object instance during dependency injection. Strategy mode: Encapsulate the algorithm into different strategy classes and specify the specific strategy through the @Named annotation.

TDD is used to write high-quality PHP code. The steps include: writing test cases, describing the expected functionality and making them fail. Write code so that only the test cases pass without excessive optimization or detailed design. After the test cases pass, optimize and refactor the code to improve readability, maintainability, and scalability.
