Closed konradbeck-creditech closed 1 year ago
@konradbeck-creditech, I am not certain that I understand what you are asking. Can you elaborate and provide some examples please?
@konradbeck-creditech from a design perspective this sounds like a compound service scenario - thus move the queries into the compound service and pass the data sets into the child service as arguments (overloaded methods if you have existing client/caller code using them directly).
an ability to cache data in a Selector or Service would be convenient, although overuse might be evidence of an anti-pattern somewhere in the code.
Is there a good way to reduce the number of queries when multiple service methods use the same selector?