In Vaughn Vernon's book Implementing domain driven design and the accompanying sample application I found that he implemented a CQRS approach to the  iddd_collaboration bounded context.He presents the following classes in the application service layer:CalendarApplicationService.java     CalendarEntryApplicationService.javaCalendarEntryQueryService.javaCalendarQueryService.javaI'm interested to know if an application will have a search page that feature numerous drop downs and check boxes with a smart text box to match different search patterns; How will you structure all that search logic?In a command service or a query service?Taking a look at the CalendarQueryService.java I can see that it has 2 methods for a huge query, but no logic at all to mix and match any search filters for example.I've heard that the application layer shouldn't have any business logic, so where will I construct my dynamic query? or maybe just clutter everything in the Query service?
How does a search functionality fit in DDD with CQRS?
design;object oriented;architecture;domain driven design;cqrs