Entity Framework (Core) Unchained: Getting the Best Performance from Your ORM - Dan Mallott
Вставка
- Опубліковано 16 чер 2024
- Entity Framework makes data access in .NET applications as easy as defining some classes, adding a connection string, and writing some LINQ statements. But listen to developers and database administrators and you will find that taking the naive approach leads to poor performance, bloated databases, elaborate workarounds, and general dissatisfaction with the technology.
It doesn't have to be this way! Behind the simple facade, Entity Framework gives us multiple options for tuning our data access and improving performance. In this talk, you will learn configuration options and access patterns that can help improve performance. You will also learn what features in Entity Framework to use judiciously or avoid entirely. Next, you will learn some strategies for structuring your database in ways that both improve performance and simplify your application code. Lastly, you will learn some tipping points about when you should discard Entity Framework entirely.
Check out more of our featured speakers and talks at
www.ndcconferences.com
ndclondon.com/ - Наука та технологія
A very informative talk about stuff we really should care about when using EF Core! And + Dan is a good speaker.
According to this, I've done absolutely everything 100% wrong lol
Some good points. Would be nice to know best approach on switching from code first to database first.
Thank you very much , I got much useful information's ,you just opened my eyes to things I should care about it before start
39:45 You can do SqlBulkCopy into a Temporary Table if you want to avoid the User Table Type.
Please share the link to slides presented in the video in description
This is all well and good, but how would you combine EF with something like DDD? In this talk you introduce a bunch of models that aren't really aggregate roots, if you have performance issues loading an aggregate like the User w/ Posts example, then it probably means the design is wrong, i.e. does a User aggregate REALLY need a collection of posts?
Why couple DDD with the ORM at all? It would be much cleaner (IMO) to have DDD-isms remain at the application layer and have your DDD models rely on repositories (black boxes to the DDD/application layer) handle persistence. Why should DDD entities concern themselves with persistence? Just my thoughts.
Using migration in Django is not painful compare to add-migration in entity framework.hope they will fix that issue
@Ryan Woods yeah, its easy
@Ryan Woods there is nothing "good" about EF migrations. Literally nothing. I could do an entire 3-hour talk on why these suck and should never ever be used. They should die in a fire.
Creating joins using ef core is a terrible idea. the lambda syntax can get real messy. is there anyway we can ensure column name consistency if we run raw sql query using ef?
Use dapper
You could look into creating views on the DB side and use EF to select and read from the view