This week, we were fortunate enough to have Brad Abrams, Kit George, Jason Zander, and Claudio Caldato visit with us. Claudio has got to get a blog, because this guy is just flat-out smart... the more I talked with him, the more I realized that there is a lot I have to learn about the CLR. We had the team visit customers ranging from J2EE zealots to bleeding-edge .NET adopters to hear everything about what customers really think about .NET.
One of my favorite discussions occurred at a customer site regarding OR mappers. I firmly side with Ted Neward on this one, but I wanted to hear someone else's opinion, especially from people who have obviously considered this space multiple times. The problem with OR mappers regards scale: they are fantastic for gaining a productive edge for small apps, but quickly break down for enterprise sites with millions of hits per day. Simply put, they just don't tend to scale, and scaling them requires more than enough work to negate the investment in OR over a data layer with optimized processing based on individual scenarios. Abstractions leak, and abstracting sets to objects or tables just hasn't been solved yet. I won't say which side of the discussion the CLR team guys came down on, but the conversation itself was fantasic, especially given Jason Zanders' insight as one of the original team members of ODBC at Microsoft.
Sitting through several of the presentations, I thought I had seen quite a bit of this material before based on presentations that I have seen at events like the MVP summit and our DPE airlift. I was wrong. The value wasn't the PowerPoint and the introduction of the feature, the value was having the guy responsible for a feature tell you how it came about, what considerations there were behind it. Here are just some of the things that I noted.
Here are some of the blog postings that I have found so far, if I missed your blog please let me know!