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.
YOU MAY ALSO LIKE:
ORMs - You're doing it wrong
Jimmy is a member of the ASPInsiders group, the C# Insiders group, as well as being the "Microsoft Most Valuable Professional" (MVP) for ASP.NET since 2009. He is also the creator and lead developer of the popular OSS library AutoMapper.