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

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.

主站蜘蛛池模板: 黎平县| 广昌县| 商都县| 晋宁县| 尼玛县| 安西县| 聂拉木县| 天峻县| 蕉岭县| 宁都县| 新乐市| 察雅县| 原阳县| 洪洞县| 揭西县| 兴和县| 怀远县| 吉木乃县| 茂名市| 平湖市| 宜宾市| 永昌县| 太湖县| 西畴县| 肃北| 建湖县| 新邵县| 西安市| 黎城县| 昔阳县| 武川县| 武义县| 娄底市| 咸丰县| 海南省| 什邡市| 桑日县| 江永县| 安义县| 洞头县| 上犹县|