This is my April post on the Donews blog, and now all go to the blog park, wind full sleeve hope to further elaborate your architecture, I will transfer this article to the blog Park. Original: Http://blog.donews.com/shanyou/archive/2005/04/23/347792.aspx
In my own capacity, there is not enough time and resources to develop a complete set of platforms. Choose from a number of outstanding projects to integrate in the many open source projects that you already have. "Standing on the shoulders of giants" is a famous quote from Newton. It is also suitable for our IT industry.
My vision of the platform's technical architecture is to use an open-source ORM framework to do the data persistence layer, which does not have the appropriate Web-layer framework to write code in ASP. NET-Code-behind way, and the data persistence layer joins the Web presentation layer with the IOC container. 1, open source Framework selection: Data persistence layer NHibernate and ibatisnet both are very good data persistence layer, NHibernate is excellent hibernate dotnet transplant version, in the open source community has very high popularity, Ibatisnet is the data Mapper framework and the ported version of the Java version of Ibatis, which is a very popular tool in the dotnet open source community. NHibernate is used to support very good object-oriented design models, Ibatisnet is used to support porting of applications (already existing databases, in production state), both of which are requirements for developers. This gives you greater flexibility. IOC containers spring.net and Castle, which are two dotnet very excellent IOC containers. Spring.net is also the Java Spring version of the migration, the current version is 0.6,castle is dotnet under the new IOC container, its function, Maturity is much better than spring.net, and the framework is ready to use Castle. The technical architecture of the final platform is nhibernate/ibatisnet + Castle + ASP. NET2, Architecture Integration: The Web layer of ASP is responsible for data input and output, response to user events, and input validation work, the Web layer on how to get NHibernate session and Ibatisnet Sqlmapper? DAO in this architecture, Service and NHibernate session and Ibatisnet Sqlmapper are managed through castle, how does the Web layer get an instance of the Castle IOC container, Refer to the article on the ASP. NET page to get an instance of the Castle container . The Web page processes business logic through the service, the service is responsible for using case logic, and domain-related logic is delegated to the domain model to implement. The service completes the persistence of the domain model through DAO. The service is responsible for the management of database transactions and NHibernate session/ibatisnet sqlmapper. Domain model is responsible for representing the data for the problem domain, and DAO uses NHibernate/ibatisnet persisted data and queries. When we implement DAO, we use Castle's nhibernate/ibatisnet DAO support, which greatly simplifies the code, and many methods are done in a simple line. This architectural advantage is clear, the level is clear, the responsibilities of each layer is clear, easy to design and development, combined with mock and castle IOC, unit test is also very easy. And the code behind the scenes (Service, domain model and DAO) does not depend on the ASP. The same code can be used on the Web app as well as the WinForm, just replace the UI layer. Links to the framework tools used http://www.castleproject.org/castle/show/HomePagehttp://nhibernate.sourceforge.net/http://sourceforge.net/projects/ibatisnet/ and here's a great article . Application System Architecture Design
dotnet Software Development Framework
