I would agree with this, however if your caching the datasets at the application level (for a web app) this wont really impact on your web servers performance too much - assuming your just reading the datasets of course barring the initial population cost.
How do people feel about caching commonly used tables (ie. an organizational structure for instance) at the application level in an ASP.Net project - does this have any catches (other then data getting stale over time and the initial population cost) - I've got plans for doing this with a number of business objects (rather then the datasets) for an upcoming application where performance is the biggest concern. Any feedback would be well appreciated as I'm embarking into this territory for a largeish project quite soon *g* - are there any threading issues with two applications accessing the same cached object in a websites application? -----Original Message----- From: Ben Kloosterman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 1:44 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Data Access API I am finding DataSets a godsend basically your DB becomes less important which is always a good thing. I am writing a Cache of DataTables to extend this further. This way I can use cheap middleTier machine cluster and a cheap database. eg most clients will get the same performance from MSDE2000 as a SunE6800 with Oracle. My thinking goes like this - If I am writing a complex middle Tier or Windows Form I use DataSets if I am using Web pages I don't - the cost is too high. ( Unless development time is important and performance is not ) Ben -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Sent: Wednesday, 12 June 2002 12:10 AM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Data Access API A number of people I have run into, and to some extend even I myself, have been confused about the use of ADO.NET datasets versus the concept of building your own Domain Object Model and using datareaders and commands to manage the db access portion of a system. I am wondering what experience the members of this list have had with ADO.NET. Have you found the productivity of a dataset outweighs the control of building your own Domain Model? What about the argument that the functionality that comes with datasets comes at a cost and frequently you don't need all that extra "stuff". Finally, is there any sort of information that determines the "cost" of a datasets functionality. By that I'm interested in an argument like " Yes certainly the dataset has extra functionality but it only adds XXX percent to the overhead of a given class or object." Maybe this isn't even a consideration at all? Anyways, the more feedback you could give the better. Or if this has been discussed on the list, could you refer me to the posts? Thanks Thomas You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
