--- "Sills, Adam" <[EMAIL PROTECTED]> wrote: > The goal of our abstracted data classes were to give us the ability, if > necessary (and I doubt it will ever be necessary), to rewrite the data layer > for any data source, and have the business layer not know the difference, > and to provide very simple access to get at your data. Both of which it > does, and it does both incredibly fast (however I am positive it wouldn't > necessary scale well to an "enterprise" system, with thousands of concurrent > users, unless you had a large cluster of webservers).
The whole 'changing the data store' gets me. I hear it a lot from OR mapping people. How often are you realistically going to do this? Is it really worth the effort? Bearing in mind switching enterprise class databases is a costly and time-consuming affair even when you don't take into account redevelopment of code. Of course I can't answer in anyone's individual case, but it often seems like overengineering to me. I'm with XPers on this - I can't remember their phrase for it, but it is along the lines of don't do it unless you have to. Peter __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
