ORM has become my new arch nemesis. The amount of suffering and lost business opportunity that is caused because the average developer can't be bothered to write a SQL query anymore has become immense.
The mainstream RDBMS engines are capable of unbelievable feats when used properly. If you insist on using an ORM, maybe look into SQLite as a provider to help mitigate the N+1 issue. If your problem is bigger than SQLite but you still cant be bothered to write custom SQL command text, you are probably going to fail in your mission.
If you look at it from a civil engineering perspective, Entity Framework is like an anti-bridge. Every time you install it somewhere, everything takes longer and costs more to do.
The mainstream RDBMS engines are capable of unbelievable feats when used properly. If you insist on using an ORM, maybe look into SQLite as a provider to help mitigate the N+1 issue. If your problem is bigger than SQLite but you still cant be bothered to write custom SQL command text, you are probably going to fail in your mission.
If you look at it from a civil engineering perspective, Entity Framework is like an anti-bridge. Every time you install it somewhere, everything takes longer and costs more to do.