StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17382837
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-29T17:24:35.017
FavoriteCount
0
LastActivityDate
2013-06-29T17:24:35.017
LastEditDate
LastEditorUserId
0
OwnerUserId
257864
ParentId
17380235
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think its important to understand why you want a n-tier architecture. If your most important requirement is simplicity, then splitting out your application into n-tiers is not really needed. However, this choice will result in a downside if you require flexibility. On the other hand, multiple tiers offer flexibility and the cost is the amount of work it takes to build them. As an example of why you would want to have a n-tier architecture, imagine this scenario. You build an application using Entity Framework 4.x. in your Data Access layer. Then EF 5.0 is then launched and you want to upgrade. If your other tiers are completely ignorant of the Data Access technology that you are using (as they should be), you should have very few issues in upgrading the DAL to a different version or database type. I stress the IGNORANT part. Each layer in the application should be IGNORANT of dependencies in other layers which will allow you to build a decoupled pluggable architecture. Its a big topic and if you have interest in learning more, I would suggest looking at Domain Driven Design techniques. Don't just have n-tiers for the sake of it. Data Transfer Objects(DTOs)are the objects that carry data between these self contained layers. That is necessary because a "Person" object in the DAL is not the same object as a "Person" object in the Business Layer. DTO's map between the two objects. Have a look at <a href="http://www.dofactory.com/" rel="nofollow">http://www.dofactory.com/</a>. You will see a simple n-tier MVC application with multiple UIs (winforms, MVC, etc) talking to a self contained Business tier. This should also give you a better understanding of where to put your projects and why they are needed.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImplementing 3-tier Architecture in MVC3
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGreg
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.