When I read about what people suggest to load 1:n relations, it makes me wonder if they know what they are doing. In Entity Framework Core, basically every LINQ expression translates into one SQL statement. When you do Include(...) on 1:n relationships (collection navigation properties), you are basically

A lot of guys are complaining on GitHub that implicit mapping for many-to-many relationships is missing for Entity Framework Core. I don't see this missing feature as too critical. With some clever patterns you can implement workarounds without affecting your business domain objects too much. I'll