Jesse Ezell Blog

<i>.NET and Other Interesting Stuff</i> <div id="ad"><script type="text/javascript"><!-- google_ad_client = "pub-1219444915196145"; /* 468x60, created 1/25/10 */ google_ad_slot = "1898962835"; google_ad_width = 468; google_ad_height = 60; //--> </script> <script type="text/javascript" src=""> </script> </div>

  • Building a Simple Web Server With WCF

    Tired of seeing a million examples of using REST support in WCF (which blows) and not a single example that goes beyond the basics everyone knows. So, I wrote a simple web server today using WCF and blogged about it:

  • Back in Action

    Everyone keeps asking me to start blogging again... so I'm finally doing it. I'm back in action after a year or so off from blogging. Been working with WCF 24/7 since joining the Neuron ESB Team and have plenty of WCF tricks to share.

  • Configuring WCF Performance

    Because the WCF team wanted to provide something secure out of the box and allow inexperienced developers to get up and running quickly, WCF will not perform well without tweaking. Here's a little help with the less obvious settings:

  • Entity Framework: Right Problem, Wrong Place

    I was listening to the recent .NET rocks episode about the Entity Framework advisory council and it was interesting to hear the team's point of view and the problems they are trying to solve with the Entity Framework. They have nice goals, but there is a fundamental problem here that some of the original database gurus like C.J. Date make quite clear. SQL is flawed. It's not that we need a million object relational mappers or that we need to look at our databases in terms of objects. In fact, that's the opposite of what the relational model was intended to do. When E.F. Codd invented the relational model, he intended for the database to be a collection of facts with relationships to other facts... not a collection of objects. The relational model was supposed to provide a way to look at and work with these facts in different ways, but SQL and modern RDBMS's fall short of what they were supposed to do. Somewhere along the way, the original plans were lost. Instead of building a truely relational storage system, vendors jumped on the semi-relational SQL model. The SQL model ties physical structure closely to the logical data model, which is where a lot of problems start coming into play. This leads to the situations we've all seen where we need to denormalize the data model to get decent performance numbers.  It seems to me that the solution to the problem should not start with mapping the data to objects, it should start inside SQL Server itself, transitioning from the flawed world of T-SQL to a true implementation of the relational model as it was intended, a world where the physical model is truely detatched from the logical model.