title: Arguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
body: <p>We develop mostly low traffic but highly specialized web applications. Normally we use L2S, EF or nHibernate as access layer and then throws Asp.Net MVC to it and in which for normal crud operations we query the ISession/DataContext directly but for more advanced functions/side effects we put it in a some kind of service layer. </p>
  
  <p>Now, i was think about publishing the data through OData (WCF Data Service) and query that from the controllers (or even from jQuery when the a good template engine shows up) and publish the service operations through a WCF service (or as custom methods on the WCF Data Service?). What advantages/disadvantages does this architecture poses? </p>
  
  <p>Do I gain something except higher complexity and latency? Better separations of concerns (or is it just a illusion)? </p>
  
  <p><strong>Edit:</strong>
  Can it be a good idea to create a complete ajax driven solution with eg. <a href="http://www.silverlight.net/getstarted/riaservices/" rel="noreferrer">WCF RIA Services</a>? Or do one loose too much flexibility? Feels like you can completely dispatch your views from your logic then, heck, one should be able to just write pure HTML, not even a asp.net MVC should be needed? but i guess there's a lot of new problems arising? </p>