BTW I just wanted to point out that our application is more of a "data warehouse", which most likely has a different domain implementation than a public-facing blog or news site. This means all of our business rules are very low-level (mostly permission-oriented), and most things are accessed via search forms.
-- Hector On Thu, Apr 15, 2010 at 10:58 AM, Hector Virgen <[email protected]> wrote: > On Thu, Apr 15, 2010 at 10:35 AM, Paul <[email protected]> wrote: > >> >> I think it's more important to concentrate on your domain AND not your >> data layer first. >> It's GOOD to have many specialized methods if your business logic works >> that way and more importantly is described that way. >> This is a concept known tell don't ask.. if your business logic is always >> asking for specialize queries / commands or anything really, >> it should exist somewhere in your domain model. >> >> Your controllers and application services should really just be asking the >> domain to do work. >> Controllers should interpret the request and pass the info to the domain >> model to do work. > > > This is true, but we also need to support a complex searches where the user > can mix and match over twenty types of criteria. It would be borderline > ridiculous to have to create methods for each combination. > > -- > Hector >
