Clever Geek Handbook

Where does ADO.net Data Services fit in N-Layer Arch?

I don't like accessing data directly from the UI layer. I somehow don't understand where to use the ADO.net data service in the N-Layer arch software.

EDIT: I am struggling with the concept of a service as a DAL. I would suggest that it is not very efficient, although it looks scalable.

+2


source to share


2 answers


I'm not an expert here, but from what I can glean from the reading I've done, ADO.Net data services seems to be a way to provide RESTful access to your EDM data model. I think the kicker is that entities are defined using an EDM definition that you are probably using in the data layer with the Entity Framework (if you can't just use WCF instead of Data Services) and change tracking with EF is the different levels are difficult and since the REST (HTTP) service is based on Etags support that allows you to track changes that ........ hopefully you get a picture ...... makes your life easier.

Now, as I said, I am not an expert, but this is what I have made of it so far (from research only). One part I'm missing though WCF has REST support, so how does it fit or where is Data Services hosted (I suppose you always need RESTful services that are not needed or want EDM)?



I would love to hear what other (more experienced) views think, since I too may be off target.

+2


source


You can use it as data access layer and use data access layer in business logic layer, for example in examples: http://www.asp.net/learn/data-access/



-1


source






More articles:


All Articles