Arguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly

Posted by Carl Hörberg on Stack Overflow See other posts from Stack Overflow or by Carl Hörberg
Published on 2010-03-23T09:40:41Z Indexed on 2010/03/23 9:43 UTC
Read the original article Hit count: 715

Filed under:
|
|
|
|

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.

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?

Do I gain something except higher complexity and latency? Better separations of concerns (or is it just a illusion)?

© Stack Overflow or respective owner

Related posts about architecture

Related posts about asp.net-mvc