.NET Data Community Standup - EF Core Architecture: Internal Dependency Injection

Join Arthur Vickers and others from the EF Team as we start a deep dive into the architecture of Entity Framework Core. This won’t be a formal talk, but rather a free-form discussion driven by the code where we look how and why things are designed and implemented the way they are. This week, we’ll start with the use of dependency injection (D.I.) and the “internal service provider.” This is the backbone of how EF Core works as a service-oriented architecture, where the core code, database providers, and plugins all implement services that work together to provide EF’s functionality.



​

#efcore #entityframework #architecture

[chaouanabil]

Thank you so much for this kind of sessions. from those sessions we don't learn just about EF Core and its intrenal we learn also how to build a better software. When you see all that small services collaborating to achieve some feature, we also see single resposibility, we IOC, depends on abtraction not implemntations principal .... i hope we will see more like this one.

[wizarrc]

This is exactly what I was looking for 2 years ago (better late than never). It would have saved me countless hours when building automated integration testing that needed custom migration logic to support nested migrations for seed data/hot fixes/etc. I never did understand the reason for using dependency objects, so much thanks for the explanation. Overall, I really loved to be able to replace classes with new inherited classes that do 95% the same thing minus a change I needed, just wish it didn't take me reading all the source code to figure out how to do it first. This is a real treat. Can't wait to see what other internals you can share. Reminds me of the Going Deep series on Channel 9 back in the day.