官术网_书友最值得收藏!

Single Tier—Single Layer Model

We will have a single project in our solution, which will have UI, BL and DAL code under a single namespace.

ASP.NET Web Project compiling into a DLL in the /bin folder and under a single namespace: MyApp

No. of project files: 1

No of namespaces: 1

There is no separation of presentation, business logic, and data access code layers. Because we will have only one assembly (or set of assemblies) that cannot be distributed independently, this model would be single tier and single layer. We can use this model for very simple projects, on which only one developer is working and where we are sure there are no major scalability or maintainability issues. For example, a personal guestbook system, small 2 or 3 page web applications, or web sites with mostly static content.

Note

Actually if you make an application based on the above model, it will follow a 3-tier architecture 'overall', if we bring the database and the browser as the other tiers and count them inside the application. This is the reason why I mentioned that for the time being we should forget about the external tiers and focus on how to break the monolithic ASP.NET application into further tiers.

主站蜘蛛池模板: 福泉市| 广宗县| 淮北市| 思南县| 丹寨县| 屯门区| 碌曲县| 梁河县| 河东区| 武胜县| 恩平市| 阿图什市| 五河县| 西盟| 仲巴县| 大田县| 南宫市| 安西县| 开化县| 巴中市| 浪卡子县| 炉霍县| 新野县| 天台县| 萍乡市| 普宁市| 榕江县| 北川| 凤台县| 绩溪县| 台中市| 汉川市| 定安县| 静安区| 定安县| 礼泉县| 承德县| 綦江县| 雷波县| 铜川市| 黄龙县|