 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / September 2005Arguments - n-Tier Architecture - DAL
Can someone give me a few arguments for implementing a DAL Layer? Why develop a BLL and a DAL in the same layer? Is it easier to scale out when you have a DAL? I can see a few benifits 1) Easy development - one group can develop and optimize dataaccess without recompling BLL 2) Its possible to switch database or have a app that can use multiple databases But in a "small" project where database is fixed to sql server - whats the benefits? Can anyone help? Thanks The DAL, if correctly designed, becomes a core framework element. This means you can use the same DAL across multiple projects. If this is the DAL you envision, the reason for having separate BLL and DAL is obvious. From another view: If you are working multiple small projects, once you solve the DAL problem for one, you can dupe it for others (or reuse, if you are talking the same client).  SignatureGregory A. Beamer MVP; MCP: +I, SE, SD, DBA *************************** Think Outside the Box! *************************** > Can someone give me a few arguments for implementing a DAL Layer? Why > develop a BLL and a DAL in the same layer? Is it easier to scale out when [quoted text clipped - 13 lines] > > Thanks on the other hand, some small projects tend to lend themselves well to going from front end straight into the back end. It depends on your defintion of small and how these applications will evolve in the longterm. If there is no longterm associated with them, what's the point of a DAL overkill? SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The Microsoft Office Web Components Black Book with .NET Now Available @ www.lulu.com/owc Forth-coming VSTO.NET - Wrox/Wiley 2006 ------------------------------------------------------- > The DAL, if correctly designed, becomes a core framework element. This means > you can use the same DAL across multiple projects. If this is the DAL you [quoted text clipped - 21 lines] > > > > Thanks I agree with you. If, for example, you are setting up a employee satisfaction site, that only needs a few questions answered, configuring for a DAL is probably overkill. It is not wise to pull out a bazooka to kill a gnat. In these smaller, or one time use, apps, I would advocate getting them set up as quickly as possible without the overhead. If, however, you find yourself writing the same software in numerous apps, you are better to refactor down to some common, reusable components. This does not mean that you do not have simpler apps at some time, but rather that core libraries speed up development in the end (like the BCL in .NET). SignatureGregory A. Beamer MVP; MCP: +I, SE, SD, DBA *************************** Think Outside the Box! *************************** > on the other hand, some small projects tend to lend themselves well to going > from front end straight into the back end. It depends on your defintion of [quoted text clipped - 31 lines] > > > > > > Thanks Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.