Usually, concepts and these concepts are different in the real world, and the design model is no exception. The design pattern is everywhere. When reading a publication or browsing website in reading technology, it is easy to find references to design patterns. So far, you are likely to read (at least over) some design patterns, such as "Core J2EE DESIGN PATTERNS" or "Design Patterns" written in Gang '. At this point, you may have some questions about the design mode. How can design patterns help me? Are they a silver? Is there any problem with the design pattern? Why can't I get design modes from Integrated Development Environment (IDE)? Several problems described above are some classic issues encountered during processing. Usually, concepts and these concepts are different from the application in the world, and the design model is no exception. This article will discuss the application of design patterns in the real world. This information can help you successfully use design patterns in your project to make the correct decision. The design pattern provides a way of sharing experience, which allows groups to benefit and avoid constant repeating inventions. Design mode usually captures the description of the problem, the context of the problem, the recommended problem solution, and the result that can be foreseen after using the solution. In order to have the most widely applicability (for more readers), design patterns are usually abstracts depending on the exact details of the environment. This abstraction produces some decodes necessary to apply design patterns to existing cases. This is an important detail: despite the design model is a good way to share professional knowledge, it usually is very important for correct application expertise. Design Mode This concept is initially generated in the construction industry. Designers (design buildings rather than computer systems) aware of them need to share ideas related to correct design technology. These ideas are formed in design patterns that the designer group will benefit from sharing experience and lessons. The design model enters the computer system field from the construction industry in the late 1980s. Object-Oriented, OO principle has gradually spread, and design model has become the best practice of cultivating new OO followers. Richard Gamma et al. (People usually call "Design Patterns: Elements of Reusable Object-Oriented Software" in Gang of Four [GOF] makes design patterns a focus of attention. As the design pattern is gradually popular, the fields they involve are gradually wide as the "Ben and Jerry" effect. For those who are not familiar with famous ice cream brands, Ben and Jerry is a supplier of ice cream products, and their ice cream products have a variety of ingredients that can be imagined (including some of you will always imagine). Therefore, it is the design pattern, and the ordinary OO design mode is the work of GOF, but it is now included in the design mode provided for development language, application servers, industry synthesis, etc. The design pattern is usually combined according to some public characteristics. The work of GOF is divided into three categories: Creational, Behaviooral and Structural. Design patterns for J2EE are usually divided into a presetentation tier, a business logic tier, and an Integration Tier. This grouping method can make the public detail that describes all design patterns more easily, or makes the classification of design patterns and discovery easier. In the discussion of the practical application of design patterns, you need to divide the design pattern into two categories: Broad Exposure and Isolated Use.
