When we create applications and the business logic becomes more complex, it might be a good idea to focus on moving business logic into the Domain Model intentionally. If you don't do this, business logic will likely bleed into view controllers. Good luck finding the scattered remains when you need to perform changes!
A Domain Model is characterized by well-named classes which hold data and provide behavior. When you do something to the data according to specific rules from your controllers, you are actually missing the opportunity to create a self-serving Domain Model. Instead, you mutate data containers from outside. The difference between a Domain Model and data container which merely wrap the persistence layer is the behavior of a Domain Model.
The Norwegian Developer Conference hosted Jimmy Bogard in 2012 for his presentation "Crafting Wicked Domain Models". It's a great 1-hour video. Jimmy demonstrates how assigning offers to members of a coupon business became a one-liner in the actual service object. He got rid of all business logic in the service object. The process is worth examining. Jimmy presents a lot of great refactorings along the way which might get you inspired.
Watch his presentation on Vimeo.
Browse the blog archive