Csla. NET Framework: Understanding logical architecture and physical architecture

I have been busy with cool mallCodeI have no time to read the books I have bought. I have time to sit down and take a good look at the books I have bought over the weekend.

Whether you want to learn a piece of knowledge or read a book, you must first know what it is, to know why it is, and finally how to do it.

Reference the original words in the book to describe this book and apply the object-oriented concept to. NET applications.ProgramArchitecture, design, and development. Focuses on business-oriented objects, that is, business objects, and how to implement them in different distributed environments including web and Client/Server structures. The book uses a large number of. NET technologies, object-oriented design and programming ideas, and distributed architecture.

Because of its limited ability, the purpose of learning is to improve the understanding of object-oriented and a better understanding of the application development process, so it will reference A Lot Of the original words in the book, because it is hard to understand, I am afraid that I will misunderstand the meaning of the author (......). Let's talk about the logical and physical architectures today.

The physical N layer refers to the physical model that distributes applications on multiple computers with different functions (such as clients, Web servers, application servers, and database servers. This is an N-layer system, but many people tend to assume that there is a one-to-one correspondence between the layer of the Logical Model and the layer of the physical model, which is often incorrect.

A physical N-layer architecture is very different from a logical N-layer architecture. The latter has nothing to do with the number of computers included in the running of applications and the network. The logic architecture is just about how to separate different types of functions. Logically, the most common layer is the UI Layer, business layer, and data layer. Physically, these three layers can be deployed on the same computer or on three different computers, the logical architecture does not define these details. The logical architecture of the application has a relationship with the physical architecture: the number of layers of the logical architecture is always no less than the number of layers of the physical architecture, the logical architecture may have more layers than the physical architecture (because one physical layer may have multiple logical layers), but it will never have fewer layers than the physical architecture.

Benefits of a good logic N-layer architecture: Logical code organization, easier maintenance, better code reuse, better team development experience, and higher code definition.

Benefits of a good physical N-layer architecture: performance, scalability, fault tolerance, and security.

As to the situations in which the n-layer architecture is suitable, I feel that I can decide from the following aspects (I just thought about it, although I still don't know how to implement it ), it is necessary when your applications are complex, and when your applications are small but large, it is also necessary when your application is very small at the beginning but may become very complicated in the future (suddenly think of a sentence in the design pattern: Using refactoring to implement the pattern ).

What is the relationship between the logical model and the physical model? When creating an application, you can differentiate functions to make it easier for the team to work together and make sure that the logical architecture has sufficient layers for flexible selection of the physical architecture in the future. Traditionally, three logic layers can be designed to share the interface, business logic, and data management of an application, the Model-View-controller and schema-data-logic layer is currently common. The physical model can be determined based on performance, scalability, fault tolerance, and security requirements. The relationship between them: the more layers the physical model contains, the worse the performance. However, the potential scalability, security, and fault tolerance capabilities become better at the same time.

Let's talk about two concepts: performance is the speed at which the application responds to users. Scalability represents the amount of performance changes as the application load increases.

In general, the physical layers in the architecture are a result of balancing performance, scalability, security, and fault tolerance. The optimal settings for a Web application and an intranet application using the Smart Client are different.

As you can see, the next section is more important. It explains how to understand each layer in a five-layer logical architecture.

Personal ads (Free Version)

As mentioned above, my abilities are limited, so I am looking for a friend or a teacher who can give me an explanation at any time. QQ: 496195436. Thank you!