- 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.
- AutoCAD 2020中文版從入門到精通(標準版)
- Photoshop CS5平面設計入門與提高
- 中文版Premiere Pro CC入門教程
- 24小時全速學會Photoshop 2021
- 中文版Photoshop CS6平面設計實例教程(第2版)
- 中文版Illustrator CC 2018基礎培訓教程
- Photoshop CS6實戰基礎培訓教程(全視頻微課版)
- 剪映短視頻剪輯與運營全攻略:視頻剪輯+音頻處理+后期特效+運營管理
- 說服力:工作型PPT該這樣做(第2版)
- SOA Patterns with BizTalk Server 2009
- Getting Started with Oracle BPM Suite 11gR1 – A Hands/On Tutorial
- 原片蛻變:Photoshop CC商業修圖必修課
- Python氣象應用編程
- 平面設計師實戰教程
- 中文版3ds Max 2020基礎教程