At the end of this article from Martin Fowler there is this sentence:
In general, the more behavior you find in the services, the more likely you are to be robbing yourself of the benefits of a domain model. If all your logic is in services, you've robbed yourself blind.
What the whole, very abstract article, doesn't tell you is what exactly goes into the service layer?
As I undestand it the architecture would be something like:
Controller -> Service(s) -> Domain Object(s) -> Repository Object(s)
So what kind of code would go into the service layer if the domain objects implement all the business logic? What would be the difference between the controller and the service layer if the service is not implementing business logic?