- ASP.NET 3.5 Application Architecture and Design
- Vivek Thakur
- 154字
- 2021-05-28 17:47:09
Single Tier—Three Layer Model
In this model, we logically break BL and DAL in different namespaces, introducing cleaner code separation.
ASP.NET Web Project that has logical separation between presentation, business logic and data access code:
- All presentation code will be under the
MyApp.Web
namespace (Layer 1). - Furthermore, the single project can have two folders:
- Business (Layer 2): for business logic code, with namespace
MyApp.Code.Business
- DAL (Layer 3): for data access code, with namespace
MyApp.Code.DAL
- Business (Layer 2): for business logic code, with namespace
Note that it is not necessary to have different folders for the logical separation of code; using different namespaces in different code files will also work fine. We can use this model for a medium-to-large web application where we know that many users won't log in simultaneously. For handling a large number of users, the application needs to be scalable, and to do this we might need to separate BL and DAL code into their own physical assemblies.
推薦閱讀
- Ext JS 3.0 Cookbook
- Blender 3D 2.49 Architecture, Buidlings, and Scenery
- Unity 2D與3D手機游戲開發實戰
- 中文版Photoshop CS6平面設計從新手到高手(超值版)
- 中文版Photoshop CS6全能一本通·全彩版
- Photoshop CS6實戰從入門到精通(超值版)
- Premiere CC視頻編輯入門與應用
- Plone 3 for Education
- Moodle Course Conversion: Beginner's Guide
- Cinema 4D基礎與實戰教程
- Configuring IPCop Firewalls: Closing Borders with Open Source
- Flash ActionScript 3.0互動設計項目教程
- VMware Virtual SAN實戰
- AutoCAD 2016中文版從新手到高手
- Oracle Modernization Solutions