How does LINQ behave when execution is split across multiple runtime contexts?

LINQ cannot preserve execution continuity across runtime boundaries such as threads, processes, or service calls.

LINQ queries rely on in-process expression trees and provider execution engines. When execution is split across threads or services, expression trees cannot be serialized or rehydrated in a meaningful way. This breaks query composability and forces materialization at boundaries, which can lead to performance and consistency issues.