Application Design - DAL (Data Access Layer) RRS feed

  • Question

  • For the past few years I've spend most of my time developing "in-house" business apps.  Because they've all been in-house and I know where the data is residing etc., I have incorporated the DAL into my Business Layer with methods like "Save", "SelectById", etc.

    I'm now beginning to venture into creating apps for others and want to start removing my DAL from my Business Objects and just wanted to know what are the best practices concerning that.

    Let's say I've written an application and I want to be able to store my data in Sql, Oracle or Xml - what's the best approach for this?  Is it simply to use the provider model to handle this?  Is it just a matter of writing a DAL interface that you can make your various DAL classes inherit from?  How then do you make your app configurable so that it can use any DAL and pass connection strings and such to it?

    What's the best practices and methods concerning all this?
    Wednesday, February 17, 2010 4:14 AM


All replies