Share business logic in csla.net

 

 In my spare time, I read some books about the csla framework I bought in the last few days.

... The remaining solution is to centralize the business logic in the business logic layer of the client (or Web Server), so that the UI Layer can access the business logic and deploy it in the business logic layer of the application server, in this way, the business logic can effectively interact with the data access layer. These two solutions offer benefits at the same time: an efficient and high-performance background processing for interactive user migration and database access (or other data sources.

When there is no application server, the business logic is deployed only once: On the client or web server.

In an idealized situation, the business logic interacts with the UICodeIt runs on the same computer, and when accessing the database, it runs on the same computer as the data access code (as mentioned in the previous lecture, all the code runs on which computer depends on the physical architecture of the system ). Business logic must provide a friendly interface for UI developers to call the data verification and processing logic. In addition, it must be able to efficiently use the data access layer to read and write data.

The tool used to solve this seemingly tricky requirement is to encapsulate the application.ProgramData and mobile business objects related to business logic. A reasonably constructed business object can be moved from one computer to another in the network, and you almost don't need to do anything. The net framework itself handles the underlying details, and you can focus on business logic and data.

If you design and implement Mobile Business Objects well, you can. Net Framework transmits your object by value in the network, that is, automatically copying the object from one computer to another. This requires a little extra code. You can move your business logic and business data to the computer where the UI Layer is located, and then transfer them to the computer where the data access layer is located when you need data access.

At the same time, if you place the UI Layer and data access layer on the same computer, then. . NET Framework will not move or copy your business objects. These two layers use them directly, so that it will not cause performance degradation or additional overhead, and you do not have to do anything about it ,. Net will automatically detect that the object does not need to be copied or moved, so it will not do any action.

The business logic layer is lightweight, flexible, or mobile, and can adapt to the physical environment where the application is deployed. Therefore, you can use a basic code library to support multiple physical N-layer architectures, so that your business objects can support multiple possible deployment scenarios without any additional code, A small amount of code that supports moving objects between computers will be encapsulated in the framework, so that business developers can focus on the development of business logic.

 

The above are some of the words that I feel very meaningful. I would like to share with you that this framework is indeed awesome *.

Because of its limited capabilities, we have developed cool cosmetics Mall (Www.koyee.net) The website has spent a lot of energy and time, and has learned a lot. If you are interested, you can give valuable comments, in the future, I will write down the problems encountered in the process and the development skills I have learned and share them with you. At the same time, I have left many questions to ask, if you want to learn more or are using the csla.net framework, you can add QQ: 496195435