#105 Jon Smith, Entity Framework Core 2.1 and Domain Driven Design

by Bryan

Summary
Jon Smith talks to me about Entity Framework Core 2.1, how to organize your EF code to meet the principles of domain driven design and his recent book on the topic.

Details
Who he is, what he does. Leaving tech and coming back. Differences between EF 6 and EF Core, no more db initializer or data validation (by default), better adding and updating, lazy loading, less bugs in Core 2. How to layout your models, DTO's, business logic, getters and setters, action methods and where to perform queries. Measuring performance and scalability of Entity Framework; Bryan rants about measuring performance yourself, Dapper vs EF, does performance always matter ; Entity Framework Extensions and Dapper Plus from ZZZ Projects. Unit testing, Ensure Created, how to test calls to stored procs with EF.

Links
Jon's site

Jon's recent article on this topic

Jon's book

Download mp3 of podcast

14 thoughts on “#105 Jon Smith, Entity Framework Core 2.1 and Domain Driven Design”

  2. Pingback: Three approaches to Domain-Driven Design with Entity Framework Core – The Reformed Programmer

  3. Great episode, interesting to hear about the experiences differing performance between ORMs.

    Also I appreciate the “you may also like episode(s)” at the end of each episode, great to hear relating or counter discussions on a topic!

  4. Great conversation. Would be interested in exploring more the philosophical difference you briefly discussed regarding logic/data access in Controllers. If there is no good way for someone else to use another’s performance metrics, do you think there are at least any best practices or things you can do to maximize their anecdotal benefit?

    • Hi Stephen,

      That topic alone would make a good podcast. I found my EF vs Dapper results were nothing like what was published on the Dapper github page, I have seen anything published by the EF team.

      Another time, I tested a bunch of serialization libraries for JSON, Protobuf and MessagePack, again my results were very different from what each of the authors were claiming. A cursory look at the project pages for these libraries would tell that many (maybe most) of them think they are better than their competitors!

      Bryan

  7. So Entity Framework Core is to Entity Framework as .NET Core is to .NET? I run .NET Core on my Linux box. Can I run Entity Framework Core as well?

Comments are closed.