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

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.

主站蜘蛛池模板: 蚌埠市| 烟台市| 元谋县| 平果县| 霍邱县| 彭山县| 松溪县| 绥棱县| 同德县| 公主岭市| 如东县| 黄陵县| 浏阳市| 文成县| 佛冈县| 体育| 凯里市| 台南县| 吴川市| 皮山县| 武邑县| 开封市| 丰都县| 宁陕县| 于田县| 西安市| 鄂温| 建昌县| 海门市| 邹城市| 汝州市| 邮箱| 北宁市| 上犹县| 天等县| 西峡县| 芜湖市| 伊吾县| 永川市| 巴东县| 文水县|