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

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.

主站蜘蛛池模板: 临桂县| 三穗县| 阿拉尔市| 曲阳县| 中卫市| 蒲城县| 宜川县| 花莲市| 那曲县| 墨玉县| 广安市| 安岳县| 广德县| 五河县| 富川| 汉寿县| 威海市| 韩城市| 大田县| 来宾市| 大竹县| 衡水市| 会泽县| 闸北区| 黄平县| 沙雅县| 阜平县| 普陀区| 惠来县| 花垣县| 三河市| 长海县| 将乐县| 双牌县| 吉首市| 合阳县| 平安县| 普兰店市| 泌阳县| 保康县| 渭南市|