title: When Building an N-Tier application, how should I organize my names spaces?
body: <p>So when I started trying to build my websites in an n-tier architecture, I was worried about performance.</p>
  
  <p>One of the guys who answered the question told me if you applied a good architecture you'd end up with even a better performance. It's related to compiling the dlls and stuff, but now I'm not sure how to name my namespaces.</p>
  
  <p>Like I have the main Namespace for my data access layer so let's say I have this namespace as my data layer ..DAL</p>
  
  <p>but now I have more than entity in the application that needs to be served by this layer, and each entity has it's own smaller entities.</p>
  
  <p>so should I include all the data code under one Namespace (DAL) or should I each entity have it's own namespace like DAL.E1 and DAL.E2 or each main or child entity should have it's own namespace like DAL.E1.c1, DAL.E2, DAL.E3.c1, DAL.E3.c2 .. last question should DAL itself include any classes or not ?</p>