
LINQ Join Queries vs. Nested Sub-Queries
Developing web applications, there are scenarios and patterns which repeat over and over, day after day, when working with the underlying data. One of these scenarios which I see very often is when there are two or more collections with one-to-many or many-to-many relationships which require filtering or joining on some type of key to ultimately perform a computation that requires the parent and the child in a hierarchy.