Join Chris Klug and me today on our latest Livestream. I think this is a spicy 🌶️ take, and I’m curious how many folks agree or disagree with the guest regarding #dotnet#entityframework?
@khalidabuhakmeh Agree, though, I would believe that what Chris is describing with his wrapper over DTO is closer to the more conventional concept of a "ViewModel" over "Model", or am I missing something? A ViewModel doesn't have to be solely designed for an UI scenario, it can be designed for e.g higher level Web API
@xoofx Honestly, I liked Chris’ style way more than I thought I would. He made some great points and, as an EF power user, gave good advice regardless of the approach folks end up choosing.
I see how it matches ViewModels, but there are some slight differences. The biggest is that relationship logic and “connections” are internal to the objects. With ViewModels, it’s more about tailoring the data for consumption, whereas his approach seemed to be about building a useable API surface.
@range_marten Depends what version you’re talking about I guess. Newer versions are pretty good. Most issues I see with EF stem from pulling too much or too little data at a time.
@khalidabuhakmeh it was 2 years ago or so. It was not the query time per se but rather the startup of the app service. IIRC it had to do with checking schema.
@range_marten Yeah, EF uses a model schema to help with change tracking. The first instantiation of the DbContext can stutter a bit, but it is not enough to make me throw it out. It depends on the size of the context.
There’s also ways to precompile and cache it, so… yeah.
Add comment