ORMs(Object-Relational-Mappers), can’t live with them, can’t live without them. I always had a love/hate relationship with ORMs. No matter if it’s NHibernate, Entity Framework or a micro-ORM solution, it always feels like too much work just to get some data in and out a database…
Therefore it’s really important to use ORMs in the correct way. Jimmy Bogard has his own opinions about ORM usage and in his presentation ‘ORMs – You’re doing it wrong’, he shares his opinions with the world.
Nothing gets DBAs more riled up than a developer infatuated with an Object-Relational Mapper. ORMs work great at mapping from relational to objects, but can be a crutch. If you want to make your DBA (and your users happy), you’ll want to use your ORM intelligently. In this session, we’ll look at application patterns, ORM features and more to discover the right way of using your ORM. We’ll also look at when to ditch your heavyweight ORM and reach for a lighter one. Finally, we’ll cover why abstracting your ORM is evil and alternatives that give us more flexibility and maintainability in the long run.