- ASP.NET 3.5 Application Architecture and Design
- Vivek Thakur
- 209字
- 2021-05-28 17:47:09
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.
- Blender 3D 2.49 Architecture, Buidlings, and Scenery
- SolidWorks2014基礎實例教程
- ADempiere 3.6 Cookbook
- 二維計算機繪圖教程:二維CAD工程師取證全程指導
- Drupal 6 Content Administration
- Creo 4.0從入門到精通
- Adobe創意大學Photoshop產品專家認證標準教材(CS6修訂版)
- Photoshop電商設計與產品精修實戰(微視頻版)
- Building Websites with VB.NET and DotNetNuke 4
- Maya 2020 超級學習手冊
- TopSolid Wood軟件設計技術與應用
- Premiere Pro基礎與實戰教程
- 構筑敏捷的開發團隊:微軟Visual Studio 2010實戰兵法
- CAD/CAE技術應用
- SketchUP草圖繪制從新手到高手