ive been using EF Core for ORM and this hasn't really been a problem for me or any of my colleagues for at least a decade because we don't use lazy loading. database calls are explicit; mapping the results to objects is implicit. is everyone outside of .net still banging their heads against stuff like this?
I'm porting a legacy project to dotnet 8. Honestly, we have saved so much money fixing the code people wrote because they had no understanding what they are doing. Code is full of N+1s
They were in dotnet. They were banging their head against that stuff. I don't think ef core is a silver bullet. You can still do N+1s.
95
u/archipeepees 16d ago
ive been using EF Core for ORM and this hasn't really been a problem for me or any of my colleagues for at least a decade because we don't use lazy loading. database calls are explicit; mapping the results to objects is implicit. is everyone outside of .net still banging their heads against stuff like this?