even someone who only knows basic SQL can update a row with a single round trip to the db (something that seems to be an "advanced operation" in EF for most people). On the other end of the spectrum doing writes with raw SQL is straightforward. Of course EF may fall on its face if you're trying to do very complex reporting queries or something like that, but it should be fine for at least 95% of the queries needed by a typical app. Building queries dynamically for searches or w/e using IQueryable is a hell of a lot easier than building raw SQL queries with string concatenation. If I had the freedom do whatever I wanted I think I'd go the opposite direction. I see this opinion (Dapper for reads, EF for writes) often and it fascinates me.
For read model (queries) we used Drapper and wrote queries in SQL.
Had been in project when we use CQRS and in write model (commands) we used Entity Framework.
0 kommentar(er)
