just enough software architecture

Layer 3: Business, IT implementation, and Interaction The future software should be a service provider in the traditional industry, and the future software should be highly interactive. Therefore, based on these two aspirations, we have come up with a three-layer architecture of future software. Or three major pieces

Abstract: Software philosophy, software path, silver bullet, Wolf, software architecture, see: top ten proposition programming rules for eliminating wolf in sequence Sage said: Gu Shen does not die is called Xuan. The door to xuanjicang is the root of Heaven and Earth. It is useless if it is stored. The key to ap

MVC to your application, and because of the strict separation of the model and the view, it is also difficult to debug the application. Each component needs to be thoroughly tested before it can be used. Once your components have been tested, you can reuse them without scruple.Based on my personal experience, since we have divided an application into three parts, using MVC also means that you will be managing more files than before, which is obvious. It seems that our workload has increased, bu

release it explicitly when exiting the critical section. 2) inflexible and inefficient. Depending on the context in which the application is running, different lock types are required for implementing the critical section. However, if the lock primitive is hard-coded to the software in every place in use, it is completely unnecessary and time-consuming to change the primitive. These modes can alleviate the above problems to simplify serialization

according to the configuration file (Struts-config.xml) Delegate the request received by Actionservlet to the appropriate action handler. In the business layer, the spring IOC container that manages the serviced component is responsible for delivering the business model component to the action and the component's collaboration Object data Processing (DAO) component to complete the business logic and to provide container components such as transaction processing, buffer pooling to improve system

There are no software development companies that do not use a three-tier architecture or higher-level architecture. For example, if your project team has three people. If a layer-3 structure is used, the job can be split into one person as the UI Layer, one person as the data access layer, and one person as the business logic layer. Everyone is responsible for

is0.125us, so here's probably the execution. theInstructions.While8.12usRelative to1ms, it was extremely short, and only accounted for the8.2%Time, so there's91.8%The free time can be given toCPUTo handle background tasks.--------------------------------------------------------------------------------------------------------------- ----------------------Step two: Message management module------------------------------------------------------------------------------------------------------------

PerformanceFor users, programmers are delivering software, providing a refreshing user interface, and avoiding system crashes is often more important than the performance of the program.There is a loose relationship between performance and code speed. This kind of work is a bit forgotten how if you're just focusing on how fast your code is running. In particular, be careful about giving up other functional areas to make your code run faster. If the sp

http://blog.csdn.net/horkychen/article/details/46612899From the point of view of architecture design (so-called composition theory), software systems are modules and interfaces.The module (Hierarchy/component) determines the division of labor, and the interface determines interaction.An API is the definition of an interface. The modules do not need to be concerned with the implementation of other modules, o

types of resources. If there is a dependency between resources, rlm for each type of resources will work collaboratively, which means they need to maintain the dependency between resources. This can be the responsibility of a central rlm for the other rlm and their dependent resources, or a separate rlm can only process the dependency between each other, and leave the management of the same type of resources to the rlm of various types of resources. In a layered

=" Wkiol1srm8vr_ovaaapzikcrxtw457.jpg "/>Then, go to the Node1 server to view the HDFs file system, whether the relevant files and directories are generated:To view the generated directory:650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/58/2E/wKioL1SrnD2T4tjMAANsBMDhnlw258.jpg "title=" QQ picture 20150106162233.png "alt=" Wkiol1srnd2t4tjmaansbmdhnlw258.jpg "/>View the file inside the specific log:Hadoop fs-cat/apache/20150106_16/access.log.node1.test.com650) this.width=650; "src=" Htt

Tags: blog HTTP Io OS ar use for strong sp1. "Open-Close" principle (OCP)Software entities shocould be open for extension, but closed for modification.It is open to extensions and closed to modifications.2. Lishi replacement principle (LSP)Where the base class is applicable, the subclass must be applicable.3. Dependency reversal principle (DIP)Dependency abstraction is required.4. dummit's Law)An object should have as little understanding as possible

Common web development software architecture 1. view requirement analysis and product PRD: Product Requirement document 2. Create a database table based on the PRD and product prototype. Pay attention to the requirements of the three paradigm, use tools to access the relational database, and quickly clear the Database concept. 3. Build a project architecture