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

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.

主站蜘蛛池模板: 图们市| 罗定市| 青铜峡市| 曲阜市| 民权县| 浦江县| 景谷| 扎兰屯市| 独山县| 夏河县| 邢台市| 崇仁县| 宣城市| 宁明县| 长沙市| 九龙城区| 丁青县| 柏乡县| 忻城县| 中宁县| 汤原县| 兰考县| 突泉县| 太谷县| 金华市| 安平县| 通许县| 丽江市| 宝清县| 镇巴县| 铁岭市| 大理市| 房产| 泸州市| 壤塘县| 拉萨市| 公安县| 锦州市| 阳东县| 南皮县| 蛟河市|