Databases
StackOverflow2013
Postsdbo
POArguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POArguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
    primarykey
    data
    text
    <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>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCarl Hörberg
    1. USCarl Hörberg
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POArguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POArguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POArguments of using WCF/OData as access layer instead of EF/L2S/nHibernate directly
      1. USJasonBirch
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload