Saturday, February 16, 2002

So my point is this - if db configuration is such a crucial aspect of scalability and performance (see item below), why is Microsoft selling the equivalent of OO-Junkfood by discouraging developers from creating a properly architected object layer between the presentation layer and the data storage layer? (I'm beginning to drone a bit about this.) Anytime I've asked about it, the answer has always been " we use datasets for scalability " 11:49:19 AM     When the first ASP.NET books appeared, everyone was using datasets as the primary resultset from a db call. Presently that has changed to datareaders. MS has some very nice performance data listed here. It goes to show you that everyone's perspective changes. I also enjoyed Scott Stanfields notes on performance of NET apps. They called it "Design Point Takeaways" Horrible abuse of the English language. The big point he makes is that DB design is crucial. Hard disks spin a lot slower than memory access. So use stored proc's instead of in-line SQL and have the DB as optimized as possible, including a ton of RAM. Makes sense. RAM is cheap and a good DB will cache stored proc's to some extend. So if you can get a lot of data access to happen in memory only, w/o hitting the hard drive, the app will fly. 11:28:31 AM

© Copyright 2003 Thomas Wagner. Last update: 6/14/2003; 4:28:39 PM. This theme is based on the SoundWaves (blue) Manila theme.