Hi Zbigniew Kozłowski,
I do not think you should worry about connection latency and LINQ. This is a major issue which should be addressed by any ORM tool you use. Connection pooling is utilized behind the scenes, so in general you should not worry about this. If you want to retrieve related data together you can benefit from the fetch optimization API we have introduced. With LINQ many of the queries you build are not propagated to the server until you invoke one of the methods that forces execution – ToList(), FirstOrDefault(), Count(), etc. Bear in mind that in order to execute a query on the database server you should have an active context which manipulates the collections of persistent objects. So, if you have an active context whose life spans several queries, you can defer their execution by not invoking eager-loading methods and execute all the queries at the same time.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items