3 ms·
I hear Entity framework and code as schema I get nervous The .Net entity framework has caused a lot of problems for clients in the past. I am not as familiar w
by ThinkBeat 4y ago
I hear Entity framework and code as schema I get nervous
The .Net entity framework has caused a lot of problems for clients in the past.
I am not as familiar with the new one in .net core which is now just .net again I think.
A huge mess managing deltas for the schema.
Often used by people who do not know SQL nor relational databases
that leads to enormously slow and resource intensive queries,
(that can be done really easy and fast in raw Sql, and once
you figure out how to EF is doing things)
schemas that are suboptimal
Once you start fighting EF to make it behave better you lose a
lot of the benefit of the abstraction in the first place…
- zeroc8 4y agoWe ran into huge problems using Hibernate. Hibernate is such a complex beast and and includes so many traps that I think it's just not worth it, at least not when you don't have an absolute Hibernate expert on board. In our case, people don't care, as long as it "works" - which of course causes a lot of performance problems down the road. I'm not opposed to ORMs in general, but there has to be a middle ground.