1. Architecture and framework design levels are different like hardware design, software design is divided into different levels. Typical software design levels are as follows:
In this figure we can see that the framework is between micro-architectures and application level. DEISGN patterns is a micro-architectures-level design, and the framework is formed by multiple design pattern and other micro-architectural elements. The object&classes, Micro-architectures, and framework are called MICRO level designs. That is, from the objects&classes to the framework, there has not been a qualitative change. for the application level to global/industry level design, it is the architecture category. From application level, it is a standalone application consisting of 0 to multiple frameworks that takes into account important issues such as the UI. The system level consists of multiple applications, each representing a different role throughout the system, which together form a system work environment. Enterprise level is also made up of system level, which usually spans multiple organizations in the entire enterprise (this is a broadly-defined enterprise). Global/industry level is made up of a wide range of system applications across the Internet and commercial markets, and business-to-trade is a globally designed application. Obviously the difference between the framework and architecture here is huge, even when compared to application level. When only one framework is used in an application, can we call it architecture? In fact, the framework is only a trivial part of the architecture. In Achitecture, when we consider the technical view, we choose either Java EE or. NET before we consider: Do you want to use Spring, Hibernate? As you can see from here, the framework is just a design decision for the technical view. 2. Architecture and framework design forces In fact, only the above description should be able to make it clear that the architecture and the framework are different. But I also want to be in the otherFurther explained. Design forces I do not know how to translate, can only explain: design forces refers to the main problems, areas and capabilities. Can only be translated into "design-oriented" bar. The Framework design forces is primarily functional, complex, and performance. From the framework's positioning and design level, its primary purpose is to help developers perform public, system functions that are needed in most applications, and how much is different. For a framework that accomplishes the functionality of the system, hides and minimizes the complexity of these system functions while providing acceptable performance, this is the design goal. for architecture, the main design force is the change. Second, all possible problems are to be considered in architecture: complexity, functionality, performance, technology, all non-functional needs, etc... 3. OOP, AOP, or FOP (Framework oriented programming)?! Do Java has a benefit, is a variety of framework technology endless, easy to use. But that's not necessarily a good thing. It feels like a lot of people are very focused on the use and research of the framework, and even more attention to the frame than the basic things such as OO, Java, and EE specifications. But some like the original Windows, with VB, VC, Delphi, or Cbuilder? It seems that some people have turned oop and AOP into FOP. In my opinion, the framework of this thing, use is possible, the study will not have to write a framework is also possible, but should not stay at the framework level. Don't waste your energy on the frame and leave it to the graduates to do it. 4. Use framework! with caution Small headline exaggerated a little, is to remind everyone. In general, the use of the framework can greatly reduce workload and make development easier. The usual use of frameworks should be encouraging. But also pay attention to: do not misuse the framework. Do not use too many frameworks in a project that is not very large, or the maintenance will be affected. Try not to use several functionally overlapping frameworks at the same time. This makes the management of project development more complex and also causes maintenance problems. In EnterprisWhen using the framework in an E-level application, a rigorous evaluation of the framework is required to ensure that its design forces does not conflict with the application of enterprise level! The framework usually does not take into account the problem of enterprise level at design time, you can not assume that it will be suitable for your enterprise application! about the architecture and framework, you can use a poem to do the knot: transverse as the ridge side into the peak, the difference between the high and low. does not know the truth, only the body in this mountain. Original Address: http://www.blogjava.net/feelyou/archive/2005/11/22/ArchitectureVSFramework.html
Architecture (Architecture) and framework (framework)
