This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Datasets, DataReaders, and Objects - oh my !
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
I apologize, but this will be my first post that I don't put everything into the excerpt, even though as a result it won't all show up in your agregator. Its just getting to be SO much work. On to the post...
I've read some seriously disturbing stuff recently. Why don't .NET developers grok scalable distributed computing? from Sam Gentile hits the nail squarely on the head saying "I find any reason I can not to use DataSets", however "DataReaders will not go over either ES or Remoting boundaries across the wire. They don't scale." is more of identifying the symptom, rather than the root cause. Don't get me wrong, I have great respect for Sam and the work that he and Robert are doing. In all fairness, I too am hard pressed to present things in an easy to understand fashion - but that doesn't mean that I'm not going to try.
Sam's statement covers the root of all evil: "From my time spent there years ago, I was much more likely to find a discussion of a distributed transactional EJB app at a local user group than some dog and pony data binding with a data grid demo that tends to permeate a lot of .NET user groups. MSDN articles on architecture tend to get low scores because .NET developers just want to put something together.You look at the MSFT Architecture main page with lots of great Architecture resources and look at the low score people have given it. Screw it they say, just show me that drop in Server control again." So, I'm actually quite happy to see these issues being raised - or the shit hitting the fan - whatever suits you.
From DataReader To DataTable illustrates the point exactly. There I commented "Do you realize that you have just tightly coupled your presentation layer to your database schema ?" and I think that quite a lot of .Net developers either didn't know, or didn't care.
Previous Topic
