IQueryable & Repositories – take 2?

by

DDD Repository should encapsulate data access technicalities:

Definition: A Repository is a mechanism for encapsulating storage,
retrieval, and search behavior which emulates a collection of objects.

It is also responsible for handling middle and end of life of domain objects. Repository interface belongs to Domain and should be based on Ubiquitous Language as much as possible. In addition to DDD book, these two articles cover almost everything you need to know when designing repositories:

Exposing IQueryable on the Repository interface is not optimal in my opinion. IQueryable is not part of Ubiquitous Language. It is a technicality, it has no domain meaning. Instead of encapsulating data retrieval Repository would expose bare data access mechanism, which essentially defeats the purpose of having Repository in the first place.

Regarding ASP.NET. This is a UI framework. Why would you allow UI framework to affect the design of you domain model? Microsoft examples often times encourage things like UI data grid binded directly to your database tables. Or, most recently, controls binded to what is referred to as Domain Model, while it is in fact Anemic Model, or simply dumb data container with gets/sets. The quote from the article that you mention (I put some emphasis):

Model binding is a code-focused approach to data-binding. It allows
you to write CRUD helper methods within the code-behind file of your
page, and then easily wire them up to any server-controls within the
page. The server-controls will then take care of calling the methods
at the appropriate time in the page-lifecycle and data-bind the data.

My interpretation of this is to ditch the model and objects and just bind your data to UI. This is probably a valid and justified approach in a lot of cases. But since the question was tagged as DDD I would say that in DDD this is called Smart UI Anti-Pattern.

More Related Contents:

  1. ASP.MVC: Repository that reflects IQueryable but not Linq to SQL, DDD How To question
  2. Deploying website: 500 – Internal server error
  3. Can some hacker steal a web browser cookie from a user and login with that name on a web site?
  4. Is trying to develop for Medium Trust a lost cause?
  5. Server.UrlEncode vs. HttpUtility.UrlEncode
  6. Fixing slow initial load for IIS
  7. Advantage of creating a generic repository vs. specific repository for each object?
  8. jqGrid: using multiple methods to filter data
  9. Why would one use a third-party DI Container over the built-in ASP.NET Core DI Container?
  10. Why does the CheckBoxFor render an additional input tag, and how can I get the value using the FormCollection?
  11. How to prevent an ASP.NET application restarting when the web.config is modified?
  12. Post-Redirect-Get with ASP.NET
  13. When should I use # and = in ASP.NET controls?
  14. bytearray to image asp.net
  15. ASP.NET page life cycle explanation
  16. ASP.NET: HTTP Error 500.19 – Internal Server Error 0x8007000d
  17. Returning JSON object from an ASP.NET page
  18. Visual Studio 2012 Web Publish doesn’t copy files
  19. Is it a good practice to avoid using Session State in ASP.NET MVC? If yes, why and how?
  20. jQuery Validation plugin in ASP.NET Web Forms
  21. Understanding ASP.NET Eval() and Bind()
  22. Why am I getting “Thread was being aborted” in ASP.NET?
  23. Slow first page load on asp.net site
  24. ASP.NET URL Rewriting
  25. Dll in both the bin and the gac, which one gets used?
  26. When should a web service not be used?
  27. Is there an #IF DEBUG for Asp.net markup?
  28. How to capture submit event using jQuery in an ASP.NET application?
  29. how to know if the request is ajax in asp.net mvc?
  30. Change Single URL query string value

Leave a Comment