- 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.
- HTML5 Multimedia Development Cookbook
- Swing Extreme Testing
- Moldflow 2010完全自學與速查手冊(模流分析·成本控制)
- DSP開發寶典
- 圖像處理中的數學修煉(第2版)
- Adobe創意大學After Effects產品專家認證標準教材(CS6修訂版)
- MATLAB 2022a從入門到精通
- OpenCart 1.4 Template Design Cookbook
- JBoss Tools 3 Developers Guide
- Solid Edge 機械設計基礎及應用
- iPad Procreate風格繪畫之美
- 24小時學會Word-Excel-PowerPoint 2010三合一
- Configuring IPCop Firewalls: Closing Borders with Open Source
- 精通AutoCAD 2013機械設計
- Alfresco 3 Cookbook