Entity Framework and high load real life?

Question

.NET

I write in .Net Core.
How justified is the use of Entity Framework in real projects with high loads? Is it worth it or is it better to choose something else?

Answer 1

EF should be used when the application has a lot of the same type of simple queries, especially if it is a fix price project.
There are, of course, goon customers who want everything to be faster, in fact, when working with them, except for EF, there aren’t really any options, they won’t give you time, let’s say, to write in Dapper. But then they usually come when a lot of people really start using the application and ask them to increase Performance, and then the bottlenecks are already rewritten to SQL (often in the form of storage).

Answer 2

Not directly justified, but if you have a layer in the form of caching (for example, Redis), then it's fine.

Answer 3

I use analog EF.
Withstands in practice a load test of 400 rps.
And you have "high loads" - how much?
Regarding concerns, I will support Bogdan: initially it makes sense to use a convenient tool wherever you want. And then do tuning - pointwise in those places where (if suddenly) it will slow down.