Contents
When should you use an ORM?
The most important reason to use an ORM is so that you can have a rich, object oriented business model and still be able to store it and write effective queries quickly against a relational database.
Is it bad to use an ORM?
Yes ORM is one of the most useful anti-patterns out there. You will understand why only if you find yourself in a practical situation where you’ll have to swap databases in a project. Or even upgrade to another version of the same database.
Why do people not use the ORM tool?
The second camp — thinks that software should concentrate on the persistence level and treat the code as incidental. People in this camp don’t use ORM because they think the program should be written so its data storage and access patterns fit naturally with the underlying data store, and all data access is controlled and explicit. So Who’s Right?
Do you need an ORM for the write model?
So, the trick is that ORMs are for the write models only. They are good at mutating data, persisting your domain model, executing OLTP operations. Don’t try to also use ORMs in the read model (unless it’s really simple), leave it to SQL and/or some lightweight ORM, such as Dapper.
Is it safe to use Orm in SQL?
Huge learning curve without ORM. Relatively hard to fine tune and debug generated SQL.Not suitable for applications without a clean domain object model. Whether or not you should use ORM isn’t about other people’s values, or even your own. It’s about choosing the right technique for your application based on its technical requirements.
Why do you need an ORM in Entity Framework?
While ORMs do spend additional time generating SQL and the resulting queries are sometimes extremely inefficient (I’m looking at you, Entity Framework), it damages performance only in sophisticated read scenarios. On the contrary, the use of an ORM in the write model often increases performance.