Concept of WCF Data Services/Ria services

ArticleDirectory

• WCF Data Services
• Data Services vs. Ria services

WCF Data Services

WCF data services (or data services for short) is another data-centric communication technology built on the WCF stack that exposes data to clients as JSON-or atom-serialized restful resources using the odata protocol. the odata Protocol specifies how a client can query, navigate, and update data exposed by a service. using this protocol, the client can communicate with the service in a restful manner by retrieving data using a standard http get call (using specially constructed URIs ), and sending updates to the server using a standard http post call.

It is very simple to publish a service in the form of rest.

1. Query: because of the introduction of a query expression, it is very convenient to dynamically change the query conditions. Because it is a dynamic execution, of course, performance will be compromised compared to the stored procedure, if the performance problem is prominent, you can also use service operations or the WCF Service for processing]
2. Because it is based on rest, it is easier to integrate services with other services.

Data Services vs. Ria services

Data Services shares a number of similarities with RIA services, and in a way you coshould consider the two to be sibling technologies, at times both jostling for attention and attempting to outdo each other. both are built on top of WCF and conform to a pattern to expose data to clients, but each has a somewhat different focus. ria services (at least for the time being) specifically targets Silverlight clients, whereas data services is client agnostic. while Ria services generates code in the client project in order for the client to communicate with the services (an aspect that concerns some developers who are against "magic" code generation that they have no control over ), data Services does not need a link to the client project, and no code generation is required. instead, Data Services provides a client library (discussed shortly) to help the client interact with the service.

It can be difficult to identify whether you shoshould use Ria services or data services in your project, and how the two differ. However, you can break it down to the following:

• Ria services has a rich model designed for the development of end-to-end Silverlight applications (with the server tightly linked with its client via the code generation process ).

• Data Services is designed simply to expose data as restful resources in a standalone manner that a range of clients can consume (such as reporting tools that can consume data exposed over HTTP and serialized as either atom or JSON ). that said, ria services can also expose data as restful resources that can be consumed by a range of clients (by enabling odata or exposing a JSON endpoint using the functionality provided in the WCF Ria services Toolkit ). also, together with its ability to share code and validation logic with the client (among the numerous other features it provides ), you will find it the best solution when writing an end-to-end Silverlight application. however, if you want your service to support a wide variety of clients without having a tight relationship to your Silverlight project, data services is a viable alternative.