Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

asp.net Tier architecture

I started out my web app as 3-tier, and had spent a lot of time on it  like this article,  http://www.dotnetfunda.com/articles/article71.aspx. Should I stay with 3-tier or should I move it to 4-tier since not that I found this article?
http://www.dotnetfunda.com/articles/article18.aspx
0
VBdotnet2005
Asked:
VBdotnet2005
3 Solutions
 
CodeCruiserCommented:
Depends on your scenario really and whether or not you want to use the classes to represent objects within your application.
0
 
VBdotnet2005Author Commented:
Would you recommend to use tier either way?
0
 
CodeCruiserCommented:
Yes tiered architecture in either way is good because it allows you separation of concerns.
0
 
CrashmanCommented:
I use 4 tier, is recommended separate behaviours from objects, this allow more flexibility.

UI
Entities (Object)
Logics
Data Access
0
 
P1ST0LPETECommented:
I recommend using a 4-Tier architecture:

1. It's really not all that more work vs the 3-Tier defined in your link above.

2. Working in the different layers of the application feels much cleaner when you're able to pass around data encapsulated in objects vs passing around a bunch of variables and DataTables.

3. Objects will typically be loaded via a SqlDataReader, which is much faster than loading data into a DataTable or DataSet, especially when dealing with large amounts of data.

4. With ASP.Net, there is lots of built in features that make user input validation easier.  When using these features, you'll typically have BAL objects and DAL objects.  The BAL objects deal with all the validation, and then they map their data to the DAL objects.  This gives clean separation, allowing the DAL to be concerned with nothing more than performing CRUD tasks.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now