Best practice for queries and WCF service

Question

What would be the best practice for the following scenario:

There is a grid to be filled and needs to be changed according to each row. For example, there is a grid filled with products, then according to each product one of the columns will be dynamically filled. Is it better to return the entire product table from the service and request it on the client side or have a service method that will return only the necessary data? The latter would mean that if there are n products in the grid, there will be n requests to this service method.

My dilemma is that for some users the table will be relatively small, and sending it to the client may not be large, but other users have a significant number of rows that will be returned (more than 15 thousand).

Thanks for any insights you can bring.

Answer 1

I would suggest creating some kind of ViewModel on the server to configure data for the client. This is similar to your second option; however, this is not done line by line. This is a server-side batch operation that supports columns so that the view does not need any special logic.

, , - , os, . , , .

.

Answer 2

- ( , - ). , .

- , , .

Answer 3

, , - granularity - . SOA , , .

" " - , -. , , .

, , - .

Answer 4

, - . 100 () 0,2 , 20 , . , , .

Edit: Another idea, if possible in your situation, is to compress the data between your client and the service. Check out this forum post . You will see big winnings if you click on heaps of XML.