I mentioned this in your previous Where Should This Code Go lesson, but I don't think there is a definitive answer and perhaps consistency is more important. Lately, it feels like the community is favoring Actions more than Services and I'd like to try out that pattern, as maybe it will feel more like a business's User Stories are coming to life to better align code with natural language.

On larger projects I've used Services with Interfaces (which require Container binding) which in turn call Repository methods. It has held up years later even though it requires more overhead to setup initially.

I do like the idea of custom Query Builders as a more elegant feeling Repo Pattern. The Query Builder methods could be called via Actions vs. Services … I think I may give that a shot in my next project to keep Controllers and Models leaner!

Should You Use Big Models or Services?